> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/account-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everyday-digital.gitbook.io/account-docs/guides/account-access.md).

# Account Access

## **Adding Access Users**

**As an Admin or Agent of an account, you can** **grant account access to users outside of your team**. For each Access User, you will be able to assign a role and limit permissions to content & features. This allows you to control what outside users can and can't see or edit. At any point, you may modify or revoke access. 

## Using Multiple Accounts

**Only Admins and Agents can give account access.** To gain access to another account, the Admin or Agent of that account will need to invite you using your registered email address.

After you have been added as an Access User, you will be able to access another account by selecting your account icon and then selecting the other account you have access to. 

### **Who has access to multiple platform accounts?**

**A licensed platform provider** can access all of the accounts on their platform for support purposes. 

**A team user or access user** can be given permission by an Agent or Admin to access one or more accounts.

**An account that has multiple platform apps** will have access to the accounts from which those apps are managed.

### **How to access and switch between accounts**

**Open your Account to see Manageable Accounts available to you.** To see which account you are logged into and which accounts you can switch to, select the Account icon/logo at the very far right at the top of your screen. You will see which account you are currently logged into as well as a list of the Accounts you have access to. \
\
**Switch between Accounts.** Select the account you want to switch to and verify access by entering your account password.

### **When is access to multiple accounts needed?**

**Multiple account access allows users to switch between accounts if needed.** It is a safe way to control access permissions. Multiple account access is ideal for:

* **Support.** Adding support experts on your platform account to assist you with debugging issues and helping customers. <br>
* **Collaboration.** Adding content contributors (reseller, agency, content creator/author or instructional designer) outside of your team to facilitate content production.<br>
* **Global Access.** If your organisation has multiple accounts on the platform, some individuals may require access to more than one account, e.g. an Admin who wants to see analytics from all accounts.

## Troubleshooting

### I need access to an account

There are two ways to gain access to an account:

1. **Request access** from the Agent or Admin of the account.
2. **Add users via Account Access.** If you are the account Admin or Agent, you can open Accounts Management, select the Account Access option and manually add users.

### My content access is limited

**Your account may have been set up with limited content access rights.** Ask the Agent or Admin of the account to check your access to features.

### I can't see a feature

**Your account may have been set up with limited feature access rights.** Ask the Agent or Admin of the account to check which features you have been given access to.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://everyday-digital.gitbook.io/account-docs/guides/account-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.