Skip to content
1stLine Docs 1stLine Docs

Access

In 1stLine by Burava, Access is where you control who can work in your organization and what level of access they have.

Open the Access Control page: https://1stline.burava.com/access/users

What you manage in Access

Access is split into three tabs:

This area uses Roles to control what each person can do.

Source of users and Teams

Burava Platform is the source of your 1stLine by Burava users.

Users are synchronized from Burava Platform into 1stLine. Use Burava Platform for the source user record and organization membership. Use Access in 1stLine to control what that user can do inside 1stLine.

Teams can also be synchronized from Burava Platform. When team sync is enabled for your organization, the Teams tab in 1stLine is read-only and manual team management is blocked. Manage the source Teams in Burava Platform instead.

When team sync is disabled, Teams are managed locally in 1stLine.

Users

Use Users to:

  • view people in your organization
  • check role and status
  • search by name, email, or phone
  • open detailed user info

If your role allows user management, you can change a user’s Role directly from the Users table.

Teams

Use Teams to:

  • create and edit Teams
  • add and remove Team Members
  • set team member role to member or lead

In the current product flow, Org Admin is the role that should manage Teams.

If team sync is enabled for your organization, 1stLine shows Teams in read-only mode and blocks manual team management in this page.

API Tokens

Use API Tokens for programmatic access to 1stLine.

In this tab you can:

  • view token name, role, status, expiration, and last-used time
  • create new API Tokens
  • edit token name and role
  • rotate a token
  • delete a token

Token values are shown one time when you create or rotate a token.

Roles in Access

1stLine uses its own Roles in Access:

  • Org Admin
  • Editor
  • Reader

These Roles are specific to 1stLine authorization. They do not need to match a user’s Burava Platform role.

For example, a Burava Platform admin can be a Reader in 1stLine, and a Burava Platform reader or member can be an Org Admin in 1stLine. Set the 1stLine Role that matches what the person should be allowed to do in 1stLine.

Practical defaults in the current product:

  • Org Admin can manage user roles and manage API Tokens.
  • Editor and Reader can view Access data, including API Tokens.
  • Team management depends on both role and whether team sync is enabled for the organization.

Guides

For step-by-step workflows, use: