# Staff & Permissions

### Overview

As the workspace owner you have full control over everything. When you invite a staff member they get a limited view of your workspace based on the permissions you assign them. They log in with their own Auxvyn account and see only the workspaces they have been invited to.

***

### Inviting a Member

1. Open your workspace and click the **Staff** tab
2. Enter the team member's email address (this must match the email they use to log in to Auxvyn)
3. Select the permissions you want to grant them
4. Click **Invite member**

<figure><img src="/files/lwzBPW6khS9dTlyCzSOp" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
They will be able to access the workspace immediately after being invited. There is no email invite flow, access is granted instantly.
{% endhint %}

***

### Permissions

There are five permissions you can assign to each member independently:

| Permission          | What it allows                                  |
| ------------------- | ----------------------------------------------- |
| **View data**       | Browse the Database tab and see player records  |
| **Edit data**       | Modify the value of existing player records     |
| **Delete data**     | Delete individual keys or entire player records |
| **Manage API keys** | Generate and revoke API keys for this workspace |
| **View staff**      | See who else has access to this workspace       |

{% hint style="info" %}
Permissions can be changed at any time. Changes take effect immediately.
{% endhint %}

***

### Permission Levels in Practice

Here are some common configurations depending on the role:

**Developer**

* View data
* Edit data
* Manage API keys

**Moderator**

* View data
* Edit data
* Delete data

**Read-only observer**

* View data

***

### What Members Cannot Do

Regardless of permissions, staff members can never:

* Delete the workspace
* Change workspace settings or the Universe ID
* Invite or remove other members
* See or modify the Open Cloud key
* Transfer ownership of the workspace

These actions are reserved for the workspace owner only.

***

### Editing Member Permissions

1. Go to the **Staff** tab in your workspace
2. Find the member you want to update
3. Click **Edit** next to their name
4. Toggle the permissions on or off
5. Changes save automatically

<figure><img src="/files/JDF2yxKy4McdAqVZAjs4" alt=""><figcaption></figcaption></figure>

***

### Removing a Member

1. Go to the **Staff** tab
2. Click the trash icon next to the member's name
3. Confirm the removal

The member loses access to the workspace immediately. Their Auxvyn account is not deleted, they simply no longer have access to this workspace.

***

### Member Limits

| Plan | Staff members per workspace |
| ---- | --------------------------- |
| Free | Unlimited                   |
| Pro  | Unlimited                   |

There is no limit on how many members you can invite to a workspace on either plan.

***

### Security Notes

* Members access the workspace using their own Auxvyn account credentials — you never share passwords
* If a team member leaves, remove them from the workspace immediately
* Regularly review who has access to your workspace, especially the **Manage API keys** permission a member with this permission can generate keys and use them outside the dashboard
* If you suspect a member has misused their access, revoke any API keys they may have generated and remove them from the workspace

***

### What's Next


---

# Agent Instructions: 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:

```
GET https://auxvyn.gitbook.io/auxvyn-docs/core-concepts/staff-and-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.