Project Access

Giving the right people access to the right information is critical, but keeping it away from everyone else can be just as important. Jigawatt Fusion has a robust, yet surprisingly flexible and intuitive mechanism for deciding who can access which Projects. It's called–unsurprisingly–"Project Access".

Having an understanding of both Team structure and Project Visibility at the User level will help you understand precisely how Access works, but this article is a great starting point.

The main thing to know is that any User listed on the Project Access page can see the Project in their Pipelines, and view and work the details. You can share a Project directly with another User by clicking (+ Add User). Teams, however, are slightly more nuanced: Users belonging to a Team that is tagged here can view and work the Project if they have "Team" Visibility.

If the User has "All" Visibility, they can access the Project even if they aren't specifically added on the Project Access page; they've got access to everything by default.

Project Owner

While there's no limit to the number of Users you can include on a Project, one User–and only one–must be designated as the Owner. Indicated by a star icon, the Owner doesn't have any special power or permissions; they simply cannot be removed from a Project unless another Owner is assigned. The Owner designation exists almost exclusively for statistical analysis; it's a data point for attributing sales metrics to the right Users.

Primary Team

Like the Project Owner, designating a Primary Team (also indicated by a star) on a Project will indicate which Team to attribute sales metrics to. Unlike Project Owner, however, indicating a Primary Team is completely optional, as are Teams themselves.

In the above example, Mary Shelley can see the Project because she's the owner. She's shared it directly with Victor Hugo, who can now access it regardless of any other affiliation he might have.. And because it's assigned to the Romantics Team, Lord Byron and Charlotte Bronte, who are Romantics with Team-level visibility, can see it. Lastly, Jane Austen and Ernest Hemingway automatically see every Project in the Company, because their Visibility setting is All.

There's no limit to the number of Users and Teams that can be granted Access to a Project.

Pointers for creating a new Project

When a new Project is created, the User who created it becomes the Project Owner by default. This can be changed by anyone with access to the Project.

The Primary Team can also be choosen right when the Project is created. For a User with "Team" or "All" Visibility, indicating a Team is optional. For a User with "Own" Visibility who is assigned to a Team, however, they must assign a Primary Team before they can save the Project.

If a User belongs to multiple Teams, they'll be able to decide which of their Teams to attribute the Project to.

Additional Reading

This article primarily discussed Access at the Project level. You may also want to read how a User's Visibility settings can affect how they see Projects. To learn about structuring Teams to further customize how Projects are accessed, visit Teams.