Permissions and visibility

Repository permission is separate from public presentation and from a Coline Code project.

Repository roles

Repository access resolves to read, write, maintain, or admin capabilities. The backend checks the requested action rather than trusting a role name from the browser.

• Read allows repository and collaboration reads.
• Write allows source and contributor mutations.
• Maintain adds repository workflow and moderation controls.
• Admin controls settings, access, credentials, and lifecycle operations.

Workspace access

A workspace can define default repository access and explicit grants for members or teams. Private repository grants stay inside the owning workspace's active identity graph.

External contributors

Someone can fork and contribute to a public repository without becoming a workspace member. This keeps source contribution separate from access to private workspace files, channels, tasks, or member directories.

Safe not-found behavior

Private objects commonly return not found to unauthorized viewers. This avoids disclosing that a hidden repository, Change Request, or Issue exists.