Contributors & Roles

Every repo-backed resource — models, datasets, agents, chips, MCP servers, workflows and prompts — can have contributors: other ChipAI.dev users you give access to its git repository.

Managing contributors

Open the resource's Settings tab (e.g. /models/<slug>?tab=settings) and use the Contributors card. Only the resource owner or a moderator can see and manage it.

• Add — type a ChipAI.dev username, pick a role, and click Add. If that user doesn't have a git account yet, one is provisioned automatically.
• Change role — use the role dropdown next to a contributor.
• Remove — click the trash icon.

Adding a contributor grants them matching access on the git server and sends them a notification.

Org-owned resources. If the resource belongs to an organization, contributors must be members of that organization — add them to the org first, then assign a role here. Personal (user-owned) resources can have any ChipAI.dev user as a contributor.

Roles

Roles run from least to most privileged. Each maps to a git permission level:

• View / Clone — read the repo and clone it.
• Commit — make commits (locally, or via the in-browser editor).
• Push — push commits to the repo.
• Merge — merge pull requests.
• Admin — manage repo settings and other contributors.

Under the hood. The git server has three permission levels — read, write and admin. Viewer and Contributor both grant read; Developer and Maintainer both grant write; Owner grants admin. The finer Commit / Push / Merge distinctions are ChipAI.dev-level labels.

Requesting access

You don't have to wait to be added — there are two self-service requests.

Request access to a specific repo

On a resource you don't own, open its Settings tab and click Request contributor access. The owner (or a moderator) sees the request on their Profile under the Contributor requests card and can approve or reject it. Approving grants you the Contributor role (git read) and notifies you.

Become a platform contributor

Brand-new accounts may be restricted Members who can browse but not publish. If so, your Profile shows a Become a contributor card — click Request contributor access to ask a platform admin to upgrade your account role. A code is not needed; an admin reviews every request and you're notified of the decision.

Two different things. A repo request grants access to one resource. The platform request changes your account role so you can create your own models, datasets and agents. Admins review platform requests from Admin → Users.

Contributors vs. Organizations

• Contributors give individual users access to one resource's repo.
• Organizations are shared namespaces where a whole team co-owns many resources.

Use contributors for one-off collaboration; use an organization for a standing team.

Next: Organizations · Your Profile.