Intentionally not using multi-home

[Ka_Nishiyama]

Until now, I have been thinking about making active use of one of Asana’s biggest features, “Multi-home tasks to avoid information silos”.
However, the reality is that “task multi-homing” can often be difficult to use.
Issues with multi-homed projects:

• It is not clear which project is the main one. (Assign Primary Project for Multi-Homed Tasks)
• People outside the project can view and comment on it.

---

I think that intentionally not using it is also an idea.
How to set up Disabling multi-homing to fully lock down a custom field.

Reference post:

• Large-scale, cross-functional projects - English Forum / Use Cases - Asana Forum

I would appreciate your advice.

[Emily_Roman]

Hi @Ka_Nishiyama, good question! You can find the option to disable the ability to multi-home tasks from certain projects via the Project Permissions settings, see screenshots below:

This feature is available on Asana Enterprise and Enterprise+ tiers, as well as the Legacy Enterprise tier.

I hope this helps!

[Ka_Nishiyama]

Thank you, @Emily_Roman .

Asana has always thought that multi-homing should be used proactively, but we have seen cases where it doesn’t fit with the structure of real organizations, so we’ve been pondering what to do about it.

We will think about how to utilize this mechanism.

[lpb]

@Ka_Nishiyama, I can’t imagine a reason to consider intentionally turning off multi-homing or discouraging its use except in cases where there’s an underlying training deficiency or existing workflow design issues.

I’m not saying multi-homing should always be used, nor should you go out of your way to use it when it doesn’t help, but to remove it as a tool for potential use where warranted doesn’t make sense to me. Maybe you’ve run into things I haven’t been able to envisage?

Thanks,

Larry

[Ka_Nishiyama]

@lpb , I understand your point of view.

I wrote my image here.

Large-scale, cross-functional projects

Overview Use Asana to manage large-scale projects(Different definition to Asana projects) involving multiple departments, clients, and partner organizations. Premise Asana Features: Asana provides a wealth of tools for open, non-hierarchical communication. Real-world organizational features: Internal communication tends to be closed within each department. When interacting with other departments, information about one’s own department is often somewhat exaggerated. Challenge To effectively…

[lpb]

I’ll reply in this topic thread:

Consider how to apply Asana to large, cross-functional projects.

For many years, I had been struggling with how to best use Asana for project management, especially when multiple departments, including clients, are involved. The reasons for this are as follows: I believe that Asana’s distinctive feature is its open communication. In reality, each department prefers closed communication within their own department. And when communicating with other departments, they tend to embellish things a little. I was struggling with how to absorb this difference in t…

Thanks,

Larry