Everything in Coroid belongs to an organisation. Projects, billing, agent capacity, policies and audit history are all owned at the organisation level, so this is the first thing you create.
Sign up
Create an account using your work email. You’ll be asked to verify the address before you can proceed — verification links expire, so if yours has lapsed, request a new one from the sign-in screen.
You’ll also be asked to accept the terms of service. Coroid keeps track of which version you accepted; when the terms change, you’ll be prompted again, and you can review what you previously accepted under Terms & privacy in Settings.
Create your organisation
Your organisation is your workspace. Give it a name that matches how your team refers to itself — it appears in the interface, in notifications, and on invoices.
One account can belong to several organisations, which lets agencies and contractors keep client work separate. Projects never cross organisational boundaries.
Invite your team
Invite people from Settings → Members. Each member holds one role:
| Role | What it allows |
|---|---|
| Owner | Full control, including billing and deleting the organisation |
| Admin | Everything except the owner-only destructive actions |
| Member | Create and run work, review results |
| Reviewer | Read the work and review it, without creating or running it |
Choose carefully. The most common mistake is making everyone an admin, which means anyone can alter the policies and Provider keys that the whole organisation relies on.
Invite beyond engineering
Member is all someone needs to submit work, and submitting work means describing an outcome — not reading code. Colleagues in support, marketing, operations or product can file requests directly, and every request still arrives as a pull request that your engineers review before anything ships.
If that is how you intend to use Coroid, invite those people early. The key constraint to plan for is who will review the results, not who is allowed to ask. See What is Coroid.
What to set up now, and what can wait
Set up now:
- Members, so the people who will review pull requests can actually see them.
- A connected repository, covered in Connect your code.
Safe to leave until later:
- Provider keys — Coroid routes through its own models until you bring your own.
- Policies, quality gates, hooks and schedules — all have workable defaults.
- Billing — the free plan is enough to run your first real task.
Next
Connect your code — give Coroid a repository to work in.