> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aeon.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Change User Roles

> Modify user roles and permissions in your workspace

User roles define what actions users can perform within your Aeon workspace. This page explains how to change user roles and the permissions associated with each role.

## Understanding User Roles

Aeon uses a flexible role-based permission system with three primary roles:

<CardGroup cols={3}>
  <Card title="Admin" icon="crown">
    **Full Control**
    <br />- User management
    <br />- Policy changes
    <br />- System configuration
    <br />- All transaction capabilities
  </Card>

  <Card title="Trader" icon="pen-to-square">
    **Transaction Focus**
    <br />- Approve and sign transactions
    <br />- View account balances
    <br />- Execute within policy limits
    <br />- Limited administrative access
  </Card>

  <Card title="Viewer" icon="eye">
    **Read-Only Access**
    <br />- View transactions and balances
    <br />- Monitor workspace activity
    <br />- Export reports
    <br />- No transaction capabilities
  </Card>
</CardGroup>

## Changing User Roles

### Modify Individual User Role

<Steps>
  <Step title="Navigate to User Management">
    Go to **Settings** → **Users** in the Aeon web app
  </Step>

  <Step title="Select User">Find the user whose role you want to change</Step>
  <Step title="Edit User">Click the **⋯** menu → **Change User Role**</Step>

  <Step title="Select New Role">
    Choose the appropriate role: - **Admin**: For users who need full workspace
    control - **Trader**: For users who need transaction capabilities -
    **Viewer**: For users who only need read access
  </Step>

  <Step title="Review Permissions">
    Review what the new role will allow the user to do
  </Step>

  <Step title="Apply Changes">
    Confirm the role change - it takes effect immediately
  </Step>

  <Step title="Notify User">
    Inform the user about their new role and capabilities
  </Step>
</Steps>

### Bulk Role Changes

For changing multiple users at once:

<Steps>
  <Step title="Select Multiple Users">
    Use checkboxes to select users for bulk role changes
  </Step>

  <Step title="Bulk Actions">
    Click **"Bulk Actions"** → **"Change Roles"**
  </Step>

  <Step title="Choose Role">
    Select the role to apply to all selected users
  </Step>

  <Step title="Confirm Changes">
    Review the list of users and confirm the bulk role change
  </Step>
</Steps>

## Role Permissions Matrix

| Permission                     | Admin | Trader | Viewer |
| ------------------------------ | ----- | ------ | ------ |
| View balances and transactions | ✅     | ✅      | ✅      |
| Export reports and audit logs  | ✅     | ✅      | ✅      |
| Execute transactions           | ✅     | ✅      | ❌      |
| Approve transactions           | ✅     | ✅      | ❌      |
| Create new accounts            | ✅     | ❌      | ❌      |
| Add/remove users               | ✅     | ❌      | ❌      |
| Modify policies                | ✅     | ❌      | ❌      |
| Change user roles              | ✅     | ❌      | ❌      |
| System configuration           | ✅     | ❌      | ❌      |

## Custom Role Configuration

### Creating Custom Roles

<Steps>
  <Step title="Navigate to Role Management">
    Go to **Settings** → **Users** → **Custom Roles**
  </Step>

  <Step title="Create New Role">
    Click **"Create Custom Role"** and provide: - Role name - Description -
    Permission set
  </Step>

  <Step title="Define Permissions">
    Select specific permissions: - Account access levels - Transaction limits -
    Administrative capabilities - Approval requirements
  </Step>

  <Step title="Save Role">Save the custom role for use in your workspace</Step>
</Steps>

### Assigning Custom Roles

Once created, custom roles can be assigned to users just like standard roles through the user management interface.

## Role Change Considerations

### Security Implications

<Warning>
  Role changes take effect immediately and can significantly impact user access.
  Always verify the change is appropriate before applying.
</Warning>

* **Privilege Escalation**: Be cautious when granting Admin roles
* **Access Removal**: Ensure users still have necessary access for their responsibilities
* **Policy Compliance**: Verify role changes align with your organization's policies

### Best Practices

* **Principle of Least Privilege**: Grant only the minimum permissions needed
* **Regular Reviews**: Periodically review user roles and adjust as needed
* **Documentation**: Maintain records of role changes and justifications
* **Approval Process**: Implement approval workflows for sensitive role changes

### Common Role Change Scenarios

<CardGroup cols={2}>
  <Card title="Promotion" icon="arrow-up">
    **Trader → Admin**

    <br />

    When a user needs additional responsibilities like user management or policy
    changes
  </Card>

  <Card title="Role Adjustment" icon="arrows-rotate">
    **Admin → Trader**

    <br />

    When reducing administrative access while maintaining transaction
    capabilities
  </Card>

  <Card title="Temporary Access" icon="clock">
    **Viewer → Trader**

    <br />

    For temporary transaction access during specific projects or coverage
    periods
  </Card>

  <Card title="Offboarding" icon="arrow-down">
    **Any Role → Viewer**

    <br />

    When transitioning users out of active roles while maintaining audit access
  </Card>
</CardGroup>

## Troubleshooting Role Changes

### Common Issues

* **Permission Conflicts**: If a user belongs to multiple groups with different roles
* **Policy Restrictions**: Some policies may prevent certain role assignments
* **Active Sessions**: Users may need to log out and back in to see new permissions

### Resolution Steps

1. Check group memberships for permission conflicts
2. Review workspace policies for role restrictions
3. Ask users to refresh their browser or restart the mobile app
4. Contact support if issues persist

<Note>
  Role changes are logged in the audit trail for compliance and security
  monitoring.
</Note>

{" "}