Overview
Start here
Getting started
Concepts
Team & ownership
Deployment regions
Guides
Custom domains
Connecting a coding agent ↗Resources
Release notes ↗System status ↗Concept · Team
Code ownership & membership
On syntica, ownership is organisation-scoped, not per-app. Every application, repository, config, and deployment belongs to exactly one organisation. You collaborate by adding people to your organisation, not by sharing individual apps.
Roles are enforced. A role is an access boundary, not a label: actions are checked against the role on every request, and an unrecognised role is denied rather than defaulted. A viewer cannot change configuration or deploy. See the security page for what that covers.
The model
User ──⟨ membership (role) ⟩── Organisation ──⟨ App / Repo / Config / Deploy
Users belong to organisations through memberships, and every resource points to its owning organisation. Any active member of an organisation can access everything in it.
Roles
Each membership carries one of three roles:
Inviting & seats
1
Click Invite member and enter an email and the role they'll receive. An invite link is emailed to them.
2
They open the link, set their name, and a membership is created with the invited role.
3
Pending invites can be resent, copied, or cancelled from the members screen until they're accepted or expire.
Seat limits. Your plan sets a maximum number of users. Active members plus pending invites count toward that limit. When seats are full, add more before inviting again.
Managing members
The members screen lists everyone in your organisation with their name, email, role, and last active time. From the row actions you can:
Change a role via the inline dropdown.
Remove a member, which frees their seat and retains history. It doesn't delete their account. You can't change or remove your own membership.
Your code stays yours
Ownership on syntica is deliberately simple: the organisation owns its apps, and its members share access. There is no per-app owner, maintainer, or collaborator list, and no ownership-transfer flow. Access changes only by adding or removing members. Whatever the arrangement, the git repository behind an app is always yours to clone, move, or self-host.
We use cookies
We use essential cookies to run the site and optional ones to understand usage. See our Privacy Policy.