Configuration¶
After installing Aegis, you need to perform some initial configuration to get the platform ready for use. This guide covers essential setup steps, including user management.
User Management¶
User management is handled under Settings > Admin Users. From this page, you can invite, view, and manage users who have access to the Aegis Platform.
Key Concepts¶
- Administrator: The administrator role provides full access to all platform features, including user management, policy creation, and system settings. It is critical to ensure there is at least one user with the administrator role at all times.
- Roles: Roles define the level of access a user has within the platform. You can assign roles to users to control their permissions.
Managing Users¶
The Admin Users page displays a list of all users with the following details:
- Name: The user's full name.
- Email: The user's email address, used for logging in.
- Provider: The authentication provider used for login (e.g., Google, GitLab).
- Role: The role assigned to the user (e.g.,
admin
). - Active: The status of the user's account.
- Actions: Allows you to edit or delete a user.
Initial Setup: Ensure an Administrator Exists¶
For a new installation, it is crucial to designate at least one user as an administrator. This user will be responsible for the initial setup and ongoing management of the platform.
To assign the administrator role:
- Navigate to Settings > Admin Users.
- Add or edit a user.
- Set the user's Role to
admin
. - Save the changes.
By following these steps, you can ensure your Aegis platform is configured correctly with the necessary user access controls in place.
API Token Configuration¶
For programmatic access to the Aegis API, such as for CI/CD pipelines, custom scripts, or other integrations, you will need to create API tokens.
To create and manage API tokens, follow the instructions in the Creating and Managing API Tokens guide. As a summary, you will need to:
- Navigate to Settings > API Tokens.
- Click + Create New Token.
- Assign a descriptive name, role, and expiration for the token.
- Securely store the token value, as it will not be shown again.
Ensure you create the necessary tokens for any planned integrations or automated workflows.