Skip to main content
Settings is the organization administration area. The primary production workflow here is team management:
  • view current members
  • invite teammates
  • resend or delete pending invites
  • change roles when your role allows it
  • remove members from the organization

Roles

The dashboard uses three roles:
RoleIntended use
OwnerOrganization ownership and full administration.
AdminOperational administration for policies, keys, and invites.
UserProduct access without administrative controls.

Capabilities

CapabilityOwnerAdminUser
Manage invitesYesYesNo
Update member rolesYesNoNo
Remove membersYesNoNo
Manage policiesYesYesNo
Manage API keysYesYesNo
Keep ownership narrow. If everyone is an owner, nobody is accountable for credential and policy changes.

Inviting Teammates

If your role allows invites, you can send an invite with:
  • teammate email
  • role assigned on join
The invite flow supports:
  • admin
  • user
Pending invites stay visible until accepted or deleted. Resend an invite when delivery failed; delete it when access is no longer needed.

Managing Members

For active members, Settings shows:
  • name
  • email
  • role
  • joined date
Owners can change member roles and remove members. The UI protects important cases:
  • the last owner cannot be removed
  • the last owner cannot be downgraded away from owner
  • if you remove yourself, your access ends immediately

Visible but Secondary Sections

Settings may also show sections for notification preferences and integration endpoints such as Slack or SIEM forwarding. Treat Members and invites as the core live administration workflow unless your team has explicitly enabled additional integrations.
  1. Invite teammates instead of sharing credentials.
  2. Use admin for operators who need to manage policies and API keys.
  3. Use user for product access without administrative controls.
  4. Keep the owner group small.
  5. Review pending invites and remove stale ones.
  6. Rotate API keys when people or apps leave the organization boundary.

API Keys

Manage the credentials your applications use to call Averta.

Policies

Configure the policies attached to those keys.