--- url: https://docs.codefox.ai/how-it-works/identity-and-access.md --- # Identity and access This page explains who is who in Foxden, what each level lets a person do, and how an app decides which records a person sees, so you can give access with confidence and predict what each person will find. Access in Foxden has two layers. Foxden Admin decides who may get into each app and at what level. Inside an app, the app applies that level, and each record's sharing level decides who can open it. ## People and agents Admin keeps one identity per email address on the server. An identity is either a person or an agent (an AI worker with a name, an address and a person who owns it), and is active or suspended. A person's name and photo are set once, on their profile in Admin, and every connected app shows them. See [Your profile](/run-your-company/your-profile). An agent never signs in to a screen. It may only hold **Can use** in an app, and never any level in Admin. See [Agent identities](/connect/agent-identities). ## The Owner The **Owner** runs the company in Admin. In Admin's console a person is either an **Owner**, who can change things, or **View only**, who can open every console page and change nothing. An Owner can manage every connected app: becoming an Owner gives the person **Can manage** in each one, and the console says so: "An Owner can manage every product. To change this, change their level for Admin first." When a new app is connected, or for Owners made before this rule, an Owner selects **Give Owners every product** on **People**; Admin never gives access on its own during an update. The last active Owner cannot be removed or suspended, so the company always has one. ## Levels in each app Each person holds a level in each app, set on **Workspace** › **People** in Admin: | Level | What it lets a person do | |---|---| | **Can use** | Does their own work in the app, and sees what is shared with members. | | **Team lead** | Fennec and Cape only. In Fennec, also sees the whole team's records and numbers. In Cape, it applies while Admin manages Cape's people. | | **Can manage** | Sets the app up for the team, and sees everything shared with managers. | | **No access** | Cannot sign in to the app. | Each app keeps its own words for its levels in its database, and Admin never turns one app's level into another app's. What a person reads on screen is always one of the words above. ## Who decides, and when it takes effect * **Getting in.** Admin checks for a live grant each time a person signs in to an app, so a person with **No access** is refused at the door. Each app also reads Admin's access feed about once a minute. An app set to enforce it (`ACCESS_ENFORCEMENT=enforce`) ends the sessions of people who lost access; an app in `shadow` mode only logs what it would have refused. `foxden init` sets Arctic to enforce, and Fennec when Admin manages its people. An app that has not yet read the feed refuses nobody. * **The level inside the app.** An app's people are managed either in the app (its own **People** page) or in Admin. When Admin manages them, the level an Owner sets becomes the person's level at their next sign-in and on the app's regular read of the feed, and the app's own **People** page no longer changes levels. When the app manages its own people, a level changed in Admin does not change the level of someone already in the app. Admin's **Server** › **Products** page shows, for each app, who manages its people. See [Give people access to the apps](/run-your-company/people). ## The sharing levels Records that people create (a meeting, a document, a space) carry one of three sharing levels, the same in every app that uses them: | Level | Who can open it | |---|---| | **Share with members** (Everyone) | Every member of your company in that app. | | **Share with managers only** (Managers) | The author, the people who can manage the app, and anyone named on it. | | **Private** | The author and anyone named on it. Not managers, and not the Owner. | People named on a record, such as invitees and recipients, can always open it, at every level. **Private** has no override for anyone: an Owner's access to every app does not open a private record. A person can also share one record with a colleague to view: "People you add can open this. They get to view it, nothing more." In Corsac this does not make someone a signer; in Arctic it does not invite them to the meeting. ### How the apps differ * **Arctic** uses the levels for meetings, with a default for new meetings on its **Company** settings. **Corsac** uses them for documents. * **Library** uses them for spaces, not single pages. A person who can manage Library can manage every space they can open, except private spaces, which stay their members' alone. Inside a space, members hold **Can read**, **Can edit** or **Can manage**. * **Fennec** has no levels per record: "Records here are visible to every member of your organization." See [Sharing](/run-your-company/sharing). ## How an app decides which rows you see Every app that uses the sharing levels asks the same shared code the same question, so the rule cannot drift between apps: 1. Records at **Share with members** are visible to every member. 2. Records at **Share with managers only** are visible to people who can manage the app. 3. Records you own are visible to you, whatever their level. 4. Records that name your email address are visible to you, whatever their level. 5. A **Private** record is never visible because of a level, only by rules 3 and 4. A person with no id or no email address matches nothing in rules 3 and 4, so a missing value refuses rather than allows. Each app also limits every query to your company. A stored value the code does not recognise counts as **Share with members** for Arctic's older meetings, and as **Private** in Library. ## Related * [Key flows, end to end](/how-it-works/flows) * [Foxden Admin, the console](/how-it-works/admin) * [Choose how people sign in](/run-your-company/sign-in)