This guide is for the person who sets CoRoid up for an organisation. It calls that person the implementer, and the organisation the customer. An implementer can work for the customer, or for a firm that the customer hires.
Get started takes one person from a new account to a merged pull request. This guide covers the rest: it fits CoRoid to the systems, rules and processes of a whole organisation.
The eight stages
Each stage produces a document or a result. The customer keeps all of them. Do the stages in order. Start a stage only when the previous one is done.
| Stage | What it produces | It is done when |
|---|---|---|
| 1 Discover | The discovery document: the customer's goals, systems, rules and the processes to cover | The customer agrees with the document |
| 2 Install | The customer's organisation in CoRoid, on the plan that the work needs | The customer's owner has the Owner role, and each implementer is a member |
| 3 Connect | The git host, sign-in, chat channels and tools, connected | CoRoid can read the repositories, and each person signs in with their own account |
| 4 Configure | Projects, Quality Control, mandates, AI profiles, automations, workflows, review rules and skills | Each rule in the discovery document has a setting, or a request to CoRoid |
| 5 Pilot | One project and one workflow in real use for two weeks | The two weeks end, and the customer decides to go live |
| 6 Go-live | The go-live checklist, signed by the customer | The customer signs the checklist |
| 7 Handover | The handover note, and the exported settings and workflow documents | The customer has them, and outside access is removed or reduced |
| 8 Review at day 90 | The day-90 measures, and a list of what to change | The customer agrees with the list |
Most of the work is in stages 1 and 4. A short discovery leads to settings that nobody can explain later.
Who decides
The customer decides. The implementer asks, proposes and sets.
- The customer names one person who decides for the customer. That person owns the organisation in CoRoid and signs the go-live checklist.
- The implementer writes down each decision and its reason. The handover note is built from these notes.
- When a need is not clear, ask the customer. Do not guess a rule.
Access rules for consultants
A consultant is an implementer who does not work for the customer. A consultant works in the customer's organisation under these rules.
- A named account for each person. Each consultant signs in with an account of their own. One account can be a member of several organisations, so a consultant uses the same account for each customer.
- No shared accounts. Never sign in as another person. Never share a password, an access token or a recovery code.
- The customer's sign-in rules. Turn on two-factor authentication in your profile. When the customer requires single sign-on (SSO), the customer gives you an account in its own identity provider.
- The lowest role that does the work. The customer invites each consultant in Settings → Members. The Admin role covers the work in this guide. Keep the Owner role with the customer. See Invite your team.
- Access is removed at handover. At handover, the customer removes each consultant, or keeps a lower role on purpose. Before that, each consultant revokes the access tokens they made. See Handover.
- No customer data outside the customer's systems. Do not copy code, tasks, cases or exports to your own computer or systems. A file that you export, such as the settings bundle, goes to the customer and stays there.
A consultant can join only an organisation on a plan with more than one member. On Free, the owner is the only member. See Plans and pricing.
Before you start
Read these pages first. The guide links to them and does not repeat them.
- How a task becomes a pull request
- What CoRoid decides, and what stays with you
- Quality policies and gates
- Settings overview
Related
- Discover, the first stage
- Export and import settings