So did we decide if each a client should get their own Team, invite clients to that team and list the projects under that OR just have a single Team (Projects), have a naming convention for each project that includes the client name and project and invite clients to each project?
I’m leaning more towards the former, seems a lot cleaner and makes the project names more readable too.
PS. One question though - are custom fields and tags shared across teams?
I echo the concerns about accidentally assigning tasks to guests who don’t belong in certain projects. We have an employee Dan and I am about to add a client Dan as a guest and want to avoid this at all costs. My idea (which I’m not sure how to implement) is to have the Guest account set up with a specific name that has a prefix to designate their company name (i.e., “NSM Dan”). It seems you can only specify the email address when adding a guest, so I’m not sure if I have any control over the guest name. I certainly don’t have the ability to change other people’s names in my organization and while I don’t mind asking the client to set up his name in a specific way, it seems like there should be an easier way to do this. Any suggestions are appreciated!
Just to answer my own question, I’m going with a team per customer for now.
I’m not expecting to have hundreds of customers (is there a limit on the number of teams?)
Another way would be to just have projects with the customer code pre-pended with a company kanban in a Project Management team that collates all tasks across all projects.
What would make this loads easier is to be able to order task by project name.
That way I can have a client only project board ordered by project name. Otherwise we have to name space every single task which is silly.
Also what would be good is to have secondary sorting -
Sort by Project Name (descending) then by Priority (ascending).
How is everyone handling guests seeing each other’s names in the dropdown option when they use the mention feature?
I am using the Asana Free version. I want to avoid cluttering by side panel with creating one team per client since I only invite clients at the project level.
Here is my setup:
Problem
The added client is automatically showing as a member of my team under “Members with access to specific projects.”
Client A can see Client B’s full email address in the dropdown field when they use the mention feature even though they are not part of the same project nor are they are team members.
Per @Marie’s response in this thread, two guests can see each other if they belong to the same team.
I am confused about the bold part of the below excerpt from the guest permissions guide.
“If two people are seeing each other as a “Private User”, they are both Guests. If Guests see this, that means they are not working in either the same team, project or task together; this is to ensure that if you’re working with clients, they cannot see one another’s names unless you want them to. Once they are both following the same task or working in the same project or team, their names will be displayed for one another.”
Questions
In the scenario where My organization and I are 5 persons, and we decide to go Premium. Can we just pay for 5 seats? and then start adding clients as guests without any further cost?
Yes, that’s right. Guests will not be charged.
Great information and thank you all for posting the various options to get clients involved in each project. We have been onboard now for a couple months and already see the value of Asana in managing our projects and work plan. A question that I think I know the answer to but will ask anyway:
We currently have 40 ongoing client projects and I would expect that to grow as we hit our busy season. There are definitely opportunities to assign certain tasks to a client as part of the information gathering process. I think it would become prohibitive to double the number of projects by setting up a separate project for each client that only has their tasks in it. Currently, when I assign a guest to follow a task, I find that they can view all the tasks in the project (which there is no need nor do I really want them to see all the work we are doing behind the scenes).
The question: is there a way to limit a guest’s view to only their tasks rather than the entire project?
@Randy_Eickhoff, Re:
Yes, you can limit a Guest’s view to only those tasks to which they are assigned or appear as Collaborators (Collaborators) for. Perhaps your guest is a member of the project right now and that’s why they have access to more? If so, remove them from the project membership (also from team membership).
For more info:
Hope that helps,
Larry
Thanks Larry. It does. We tried to test this before and must have been adding them to the project rather than the individual tasks. Still need to evaluate how it the process will work but nice to know the functionality is there.
Hello- Great thread here! I currently design boards in Asana for clients, optimizing their workflows. I do not work always work within the boards do PM. Often, I need to hand it off to the client at the end. Usually, I work within their organization as a guest but I would love to be able to stay in my own space and work.
My question is if I create a project in my own workspace and then invite the client as a guest. When the design is complete, can’t I make them the owner and wouldn’t it then transfer to their workspace/organization?
This seems so easy but I know there has been a ton of convo about the handoff in the forum. Will my idea not work and why?
Thanks-
Sara
HI @hellosaraflowers. Unfortunately it won’t work. Projects are tied to the workspace/org they are created in, and can’t be transferred across. Thus your client will be the project owner only in your workspace.
This thread has been so helpful! Thank you all!
Last year, my team and I have been tracking projects using Asana (for internal team) and sharing bunch of Google Doc and Google Sheets with our clients. I am really hoping to transition into a more uniform process where my team and our clients can track the project using just Asana. I have already created a project template that I plan on duplicating for each client. I absolutely love the Timeline and Progress sections and I think my clients will do too.
We currently have Business organization and the way I have it set up now is I have created a Team called “Clients” and then creating a template for each client and adding him/her as project member. This will allow the client to see the Timeline and Progress sections of the project as well as accessing the Conversations, Board and other features within a project. Doing this will also allow each client to only view his/her own project.
The problem I came across is I cannot hide individual tasks that are only applicable to my team within each project. Is there a way to share a project with a client but limiting the type of tasks they can see?
Any advice is greatly appreciated!
Hi @anon94874620. Unfortunately you can’t have a task within a project that is private to only select project members. You can have a private task that is not associated with a project (private to only the task collaborators). In your case, you obviously don’t want the latter.
One option would be to have “client x - internal” project which is worked only by your team and then duplicate the key tasks or milestones for “client x - viewed” project. Since tasks can be assigned to multiple projects (up to 20), this would allow you to update both projects key tasks at the same time and allow private tasks or conversations to happen internally.
Here is a few past discussions around this similar topic. Hope it helps. Private task with shared project - workaround . and Professional services firms: how have you set up Asana to balance internal vs external communications with clients?