--- title: Your organisation and roles description: Who can do what in a Kaviris organisation, and how coding agents fit in. --- # Your organisation and roles Apps belong to an **organisation**, not to one person. When you sign up you get one, and you are its owner. You can invite others, and one person can be in several organisations. ## Roles | Role | Can | |---|---| | **owner** | Everything, including billing, moving ownership and deleting the organisation | | **company-wide admin** | Everything an owner can except billing, ownership and deleting the organisation: every app in the organisation (also apps in groups they are not in), its members and their rights on each app, agents, [GitHub](github.md), [policies](org-policies.md). Their sign-in also keeps the free apps up ([inactive apps](inactive-apps.md)) | | **member** | Create and deploy apps, change and approve contracts, set secrets, read logs and metrics | | **app-member** | What a member can, on the apps it is given for only | An owner makes someone a company-wide admin on the **Members** page (with a passkey). A company-wide admin gives a person **app-member** on one app (`POST /v1/apps/{app}/assignments`, with a passkey). More roles (someone who only looks, someone who only sees billing) may come later. ## When the owner is gone If nobody can act as owner any more (the owner left the company, and nobody else is owner), contact Kaviris support. A person from the company shows they may act for it (for example a company registration extract that names them as a signatory), support checks it, Kaviris approves, and the ownership is moved to a member of the organisation. The former owner's address is told. While the case is open, nothing in the organisation is deleted. Deleting an organisation, and your own account: see [Your account, your data, and deleting them](your-account.md). ## Coding agents A coding agent acts **for you**, and never with more than you have. Each agent has an [agent key](agent-keys.md) you can narrow, limit to some apps, give an expiry, or revoke. Sensitive actions (deleting, restoring, linking GitHub, and whatever else your organisation chooses) an agent only asks for: a person [approves](approvals.md) them in the portal with a passkey, and they then run once. Connecting the GitHub App and downloading a database export are always done by a person. Every action is recorded: who, through which agent, and what changed. ## Support access Kaviris support sees almost nothing about your app unless you let it. You can give a **case grant**: access for one support case, for 1 to 72 hours, that you can withdraw at any time. See [Support, and how we use AI](../support.md).