Module access

Not every project needs every module. Module access lets you enable the modules a project actually uses and govern who can reach them, so the workspace stays focused and access stays controlled.

Enabled modules

Each project has a set of enabled modules — the modules that appear in the sidebar for that project. Enabling only what a project needs keeps navigation clean and prevents work from landing in the wrong place. A module that isn’t enabled simply doesn’t appear for that project.

Access by role

Beyond enabling a module, access is configured by role. For each role you can set the default access to a module, so a contributor, a quality manager, and a viewer can each have the appropriate level. Because access is role-based, granting someone a role gives them a consistent, predictable set of module permissions.

Effective permissions

Module access combines organizational defaults, the project’s configuration, and a person’s role. To make the result clear, you can preview effective permissions — the actual access a given role ends up with on each module — before saving. This removes the guesswork from layered settings and lets you confirm access is exactly what you intend.

License ceiling

Access also respects your organization’s license ceiling — the entitlements available under your plan. If a module is limited by licensing, that limit is reflected here, so what you grant always stays within what your license permits.