> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/settings/access/users.md). # Users Invite users to your Anedot fundraising account, resend or revoke invitations, change a user's permission set or Team, and remove users in Settings > Access. **Users** are the people who can sign in and work in your fundraising account. You manage them in **Settings > Access > Users** and **Settings > Access > Invitations**. This article covers how to invite a user, manage pending invitations, assign a Team, change a user's access, and remove a user. ## Before You Begin * To invite, update, or remove users, you need **Access Management: Edit Users** permissions. Without them, you can view the Users list but can't make changes. * You can't change your own permission set, and you can't change or remove someone whose permission set gives them more access than yours. * The **Owner** can't be changed or removed from the Users page. To change the Owner, see [Organization Information & Account Ownership](/settings/setup/organization-information-account-ownership.md). ## Invite A User To invite a user: 1. Go to **Settings > Access > Users**. 2. Click **Invite user**. 3. Enter the person's **Email**. 4. Choose the permission set the person should have. **Standard** is selected by default. 5. Click **Send invite**. If your account uses Teams, invite the person with the right permission set first. Once they've accepted the invite, assign them to a Team from their user details, as described in Change A User's Access below. See [Teams](/settings/access/teams.md). The person receives an email invitation. If they don't have an Anedot login yet, they create one with the same email address the invitation was sent to. {% hint style="info" %} If the invitation email doesn't arrive, ask the person to check their spam folder. If it still doesn't arrive, contact our Support team at . {% endhint %} ### Manage Pending Invitations Invitations stay in **Settings > Access > Invitations** (the **Invitations** tab) until they're accepted or revoked. The list shows each invitation's **Email**, **Permission set**, **Status**, **Invitation date**, and **Age**. Invitations don't expire. To resend or revoke an invitation: 1. Go to **Settings > Access > Invitations**. 2. Find the invitation. 3. Click **Resend** to send the email again, or click **Revoke** to cancel it. 4. If you clicked **Revoke**, click **Revoke invite** to confirm. After you revoke an invitation, its link no longer works. ## Change A User's Access The Users list shows each person's **Name**, **Email**, **Permission set**, and **Team**. You can search the list or filter it by role. To change a user's permission set or Team: 1. Go to **Settings > Access > Users**. 2. Click the user's name. 3. Under **Role assignment**, choose a new permission set. Permission sets with more access than your own are grayed out. 4. (Optional) Under **Team assignment**, choose a Team, or choose no team to give the user full access. Assign a Team only after the user has accepted their invite. 5. Click **Save**. To change what a permission set includes, edit it from **Settings > Access > Roles**. See [Permission Sets](/settings/access/permission-sets.md). ## Remove A User To remove a user: 1. Go to **Settings > Access > Users**. 2. Click the user's name. 3. Under **Remove user**, click **Remove**. 4. Click **OK** in the confirmation prompt, "Remove this user from the account?" The user loses access to your fundraising account right away. Their Anedot login isn't deleted, and their access to other Anedot accounts doesn't change. Any webhooks and email notification settings they set up for your account are removed. ## Default Permission Sets Every account includes four built-in permission sets. They're marked **Managed by Anedot** and can't be edited. | Permission set | What it includes | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Owner** | Every permission, plus ownership of the account. Each account has one Owner. | | **Super Admin** | Every permission except ownership. | | **Admin** | Every permission except ownership and **Billing Agreements: Edit**. | | **Standard** | **Action Pages:** View and Edit. **Finance:** View Transactions and View Commitments. **Billing Agreements:** View. **Relationships:** View Contacts and Edit Contacts. **Integrations:** View. | If none of these fit, create your own. See [Permission Sets](/settings/access/permission-sets.md). {% hint style="info" %} Email notification preferences belong to each user. Each person manages their own from the profile menu in the top-right corner. See [Notifications](/get-started/security/notifications.md). {% endhint %} ## Related Articles * [Permission Sets](/settings/access/permission-sets.md) * [Teams](/settings/access/teams.md) * [Connected Accounts](/settings/access/connected-accounts.md) * [Account Security Updates](/get-started/security/account-security-updates.md) * [Notifications](/get-started/security/notifications.md) * [Organization Information & Account Ownership](/settings/setup/organization-information-account-ownership.md) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.anedot.com/settings/access/users.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.