Set primary departments and project-creation exceptions
Control where Members can create projects without changing access to existing work.
Project creation governance answers where a person may create or publish a project. Use Space and project access controls to decide which existing work they may read or edit.
Who can configure it: workspace Owners and Admins, from a member record in Team.
Set a Member’s primary department
- Open Team in the correct organization and select the member.
- Confirm their organization role and that Spaces access is enabled.
- Find Project creation governance.
- In Primary department, select the department Space.
- Check the effective indicator in the Project creation list. Wait for the update to finish before leaving the record.
- Separately configure access to the Space or the specific projects they should use.
Only eligible, active company Spaces appear here. A department selection is not an invitation, a Space membership, or a project-sharing action.
Allow creation in an additional department
In the same Project creation list, choose Allow beside another department. This records an explicit exception. For example, a Marketing Member can have Marketing as the primary department and an exception for Client Services when they regularly create joint delivery projects.
The primary department and an explicit exception can both exist for the same Space. They are independent. Removing the exception does not remove authority supplied by the primary department. Clearing the primary department does not remove authority supplied by an exception. To withdraw both, inspect both settings.
How organization roles affect the result
| Person’s state | Effect on departmental project creation |
|---|---|
| Owner or Admin | Can create projects in every eligible department; a primary department is organizational metadata. |
| Member with Spaces enabled | Primary department and explicit exceptions determine authorized destinations. |
| Member with Spaces disabled | Configured departmental authority is not currently effective. |
| Viewer | Cannot create projects; a recorded department is organizational metadata. |
A Member can also use the available personal unpublished-project flow. That does not authorize publication to an arbitrary department.
Check access separately
Suppose Jamie’s primary department is Finance. Jamie can be authorized to create a new Finance project while having no access to existing Finance projects. Conversely, Jamie can edit a shared Marketing project without being allowed to create new projects in Marketing.
A department label in navigation may provide a creation destination. It is not proof that all work in that department has been shared. Check the actual project or Space in Team’s Inventory when diagnosing visibility.
If the destination is unavailable
Confirm the correct organization, Spaces access, organization role, active destination, primary department, and exceptions. If the member can create at the Space’s top level but not inside a folder, check the additional Space write requirement for that folder operation. Do not broaden the person’s organization role just to solve a missing creation destination.