Project access

Project access controls who can find, edit, review, or manage work.

In the current workspace model, access is primarily driven by workspace membership and roles. If your product UI exposes project-specific access controls, use the UI as the source of truth.

Workspace roles

RIB Creative uses workspace roles such as owner, admin, and member.

Role	Typical permissions
Owner	Owns workspace-level control, billing context, and high-risk administration.
Admin	Manages members, settings, and many workspace operations.
Member	Works in the workspace based on available permissions.

The exact permissions may vary by plan and product version.

Access principles

• Give people the minimum access they need.
• Limit admin access.
• Remove people when work ends.
• Keep sensitive projects in restricted workspaces.
• Review access before publishing.

Before sharing a project

Check:

• Is the workspace correct?
• Does the teammate need edit access or only review context?
• Does the project contain client or sensitive data?
• Is the project ready for feedback?
• Are there unpublished or experimental changes?

FAQ

Can project access differ from workspace access?

If project-specific controls are available in your product version, use them. If not, assume workspace access controls who can reach the project.

Should every member be able to publish?

No. Publishing should be limited to people who understand launch risk, project readiness, and workspace rules.

Can I share a project without inviting someone?

Use the safest sharing option available for the project. Do not share account credentials.

Next steps

• Invite teammates: People
• Collaborate safely: Collaboration
• Publish carefully: Publish your project