Help centre · Managing
Who can do what in Diavi?
The groups shipped by default, how to create your own, and why costly rights are flagged.
What someone may do comes from their group. Diavi ships five — owner, admin, manager, developer, viewer — but nothing ties you to them: create as many as your organisation needs, from Groups and rights.
Why does the menu change from person to person?
A menu entry appears because the person holds the right that opens that screen. There is no separate list of permissions and display toggles: removing a right hides the entry and closes the API at the same time. A menu showing an unreachable page, or hiding an open one, is not possible.
The change takes effect immediately, with no need to sign in again.
What do the shipped groups hold?
Owner — everything, including the subscription, the account's Git token and its deletion. The person who created the account.
Admin — the sensitive configuration: models per agent, token caps, correction attempts, contexts.
Manager — the workflow: target branch, label on merge requests, viewing members. Real authority over how work is done, none over what it costs.
Developer — launches runs, answers the agents' questions.
Viewer — read only.
Those five can be edited and emptied freely. Only their deletion is refused: their members would be left with no rights at all.
How do I create a group?
In Groups and rights, give it a code (lowercase and dashes, it will not change) and a name, then tick what it opens. Rights are grouped by domain, and two markers warn you before you tick:
- cost — this right changes what you consume (models, caps, number of attempts);
- sensitive — this right exposes amounts or allows creating colleagues.
Neither is forbidden: it is your organisation. They are flagged so that granting them is a decision rather than a distracted click.
Why separate workflow from cost?
Because a more powerful model multiplies your consumption, and whoever arbitrates how work is organised is not necessarily whoever holds the budget. One consequence to know: a change mixing a workflow setting with a cost-affecting one is refused whole, never half applied.
Can a member use a cheaper model for their runs?
Yes, from Preferences → Display → Model for my runs. The list only offers models that cost no more than what the account already uses, and the choice applies agent by agent, only where it costs less: an agent already on a small model is never moved up. A dearer model is refused at launch, by name. An administrator can turn this choice off in Preferences → Pipeline → Execution.
Can preferences be proposed to the whole team?
Yes. An administrator opens Preferences → Display or Appearance and switches to Team defaults: what they set there applies to every member who has not made their own choice. Nothing is imposed: a member's choice always wins, and changing a default never touches choices already made. Everyone sees where a value comes from and can go back to the team default in one click.
How do I add someone?
From Members, picking their group from the list — the five shipped ones as well as those you created. Diavi can list the members of your GitHub organisation or GitLab group so you do not have to type them one by one.
How does everyone sign in?
With their forge, in one click: GitLab or GitHub proves who they are, and Diavi keeps no secret. An email and a password can be added in Preferences → Sign-in and security; that password belongs to the person, not to a space, is hashed and never readable, with an optional second factor. Rights do not depend on the way in: the group decides.