Collaborators and access control
Project owners onboarding teammates and anyone confused about missing settings access.
Owners govern projects, settings, and seats; collaborators get project access without owner-only controls. Plan limits apply immediately when you add people.
Access is role-based and GitHub-backed. Adding someone grants both tnc-sh project visibility and push access on the linked repository — plan seats count every active collaborator.
4 sections4 key takeaways3 related guides
Quick highlights
Access is role-based and GitHub-backed. Adding someone grants both tnc-sh project visibility and push access on the linked repository — plan seats count every active collaborator.
Confirm role expectations before onboarding contractors — collaborators cannot self-serve access to billing, keys, or danger-zone actions.
What you will learn
- Owners manage settings, keys, collaborators, and destructive actions.
- Collaborators work in project views but cannot open owner-only settings tabs.
- Seat usage is shown in Settings → Access & automation before you hit hard limits.
- Remove inactive collaborators promptly to preserve emergency seat headroom.
Sections in this guide