--- url: https://docs.codefox.ai/run-your-company/people.md --- # Give people access to the apps This page lets you, as an Owner, bring people into your company in Foxden Admin, give each person a level in each app, take access away, and keep at least one Owner in charge. ## Before you start * You are an Owner in Admin. * At least one way to sign in is set up (Google, Microsoft or the email link). Until one is, the Invitations page says **Nobody you invite could sign in yet**. See [Choose how people sign in](/run-your-company/sign-in). ## Levels Every person has one level in Admin and one level in each app. **No access** is the level of everything you have not given. | Where | Levels | What they mean | |---|---|---| | Admin | **Owner**, **View only** | An Owner runs the suite and can change everything in Admin. View only opens every Admin page and changes nothing. | | Each app | **Can manage**, **Can use** | Can manage sets the app up for the team and sees the team's work. Can use does their own work in the app. | | Fennec and Cape | **Team lead** | A level between the two, for someone who leads a team in that app. | In the People table the cells shorten these to **Manage**, **Lead**, **Use** and **View**. ## Find a person 1. Open **Workspace** › **People**. The table has a row for each person and a column for Admin and each app on your server, with the person's level in each cell and their **Last sign-in** at the end. 2. Type in **Search by name or email** to narrow the rows. 3. Choose **All**, **Active** or **Suspended** to filter by status. 4. Choose a product under **Has access to** to see who can use it, or **Nothing yet** to see who has no app. ## Invite someone Admin does not send invitation emails. It gives you a personal link, and you send it to the person yourself. 1. On **People**, select **Invite someone**. The **Invitations** page opens. 2. Type their **Email**, and their **Name** if you want your team to see it before they sign in. 3. Under **Product access**, choose a level for each app they need. Everything starts at **No access**. 4. Select **Create invitation**. Admin shows the link once. 5. Copy the link and send it to them. It expires in 7 days. When they open the link they see **You've been invited**, with the access it gives. They must sign in with the address the invitation names: the invitation only works for that address. Their levels apply when they accept. Below the form, the Invitations page lists every invitation still waiting, with what it gives and when it expires. Expired invitations leave the list. To cancel one, open its actions and select **Withdraw**. The link stops working at once. A second invitation to the same address replaces the first, and the earlier link stops working. ## Change what someone can use A person's record holds one row per app and one **Save** for all of them. Nothing changes until you save. 1. On **People**, select the person's row or name. Their record opens in a panel. The arrows at the top step to the previous or next person in the table. 2. Under **Access**, choose a level for each app, or **No access** to take that app away. 3. Select the save button. It counts your changes: **Save 1 change**, **Save 2 changes**. 4. Confirm if Admin asks. It asks when you make someone an Owner, when an Owner steps down, and when you remove an app from someone. The message after saving lists what was saved, for example "Saved. Fennec: Can use." ### When the change reaches the app Giving and removing access reach the app within a minute. A session the person already has open stays valid until then. A changed level (for example from **Can use** to **Can manage**) is different. Each app either follows the level set in Admin or keeps its own level for people already in it. The record says which, under **How access changes apply**: * An app that follows Admin applies the new level at the person's next sign-in. * An app that keeps its own level does not change for someone who is already in it. Change their level on the app's own People page. For someone who has not signed in to the app yet, the level you set here is their level on first sign-in. When an app holds a different level from Admin's, the row says so, for example "Arctic has them at Can use." To let Admin manage an app's people, open **Server** › **Products** and use **Let Admin manage its people** on that app. ## Owners * **Making an Owner gives every app.** When you set someone's Admin level to **Owner**, Admin also gives them **Can manage** in every app on the server. Their app rows then read **Can manage, as Owner**. * **An Owner's apps cannot be lowered.** Admin refuses with "An Owner can manage every product. To change this, change their level for Admin first." Change their Admin level to **View only** or **No access** first; they keep their app access, and you can then change it like anyone's. * **A new app does not reach Owners by itself.** When an app is connected after someone became an Owner, People shows a notice that some Owners do not manage every product yet. Select **Give Owners every product** to apply it. * **There is always one Owner.** Admin refuses to remove, step down or suspend the last active Owner: "This is the last active workspace owner. Make someone else an owner first." * **You cannot suspend yourself.** It would take away your own way into Admin. * **Private stays private.** An Owner does not see items people marked private in an app. See [Sharing levels](/run-your-company/sharing). ## Suspend or reinstate someone Suspending signs a person out of Admin and removes their access to every app. Their work stays where it is. 1. Open the person's record. 2. Under **Suspend**, select **Suspend** and confirm. To suspend several people at once, tick their rows in the table and select **Suspend** above it. To let someone back in, open their record and select **Reinstate**. Reinstating does not give their access back: set each app's level afterwards and save. There is no bulk reinstate. ## Keep people in step with a company directory If your company uses Microsoft 365 or Google Workspace, its groups can give people their app access. 1. On **People**, under **Joining**, open **Company directory**. 2. Select **Connect Microsoft 365** or **Connect Google Workspace**. The person who runs that directory for your company approves the request. Admin can only read people and groups, never change them. If the provider is not set up yet, the page leads you to **Server** › **Connections** first. 3. Under **Rules**, choose a **Group** (or **Everyone in the directory**) and a **Product and level**, then select **Add rule**. The first matching rule wins. 4. Select **Preview** to see what a sync would change, then **Apply**. A sync runs when you connect and when you select **Sync now**; there is no schedule. A person whose address is on a domain the directory has verified is suspended when the directory drops them. **Disconnect** stops syncing and keeps the people and access it made. ## Agents An agent is an assistant with a name and access of its own, and a person answerable for it. It never signs in and can only hold **Can use**. Select **Add agent** on People to create one, then give it access on its record. Its keys and unattended sign-in are covered in [Agent identities](/connect/agent-identities). ## Troubleshooting ### The person lost their invitation link Admin keeps only a fingerprint of the link, so it cannot show it again. Create a new invitation to the same address; it replaces the old one. ### "already has an account here" The person is already in your company, so an invitation would do nothing. Open their record on People and change their access there. ### "Suspended: reinstate them before giving access." You cannot give access to a suspended person. Select **Reinstate** first, then set their levels. ### A level change does not show in the app The app keeps its own level for people already in it. Change it on the app's People page, or let Admin manage that app's people from **Server** › **Products**. ### Someone still has access after you removed it An app reads access changes about once a minute, and a session already open stays valid until then. If it lasts longer, open **Server** › **Products** and check that the app is connected and has heard the latest access changes.