Managing Organization

Introduction

All user and organization access management in Bright has been built around several simple terms. Each term has several adjustable parameters to ensure that every organization and user structure can be covered by the tools presented in the Bright app.

You can operate access management in Bright using these terms:

• Organization - a logical entity containing all the users, groups, and resources in a given scope.
• User - a single organization member. Users can be combined into groups. Each user has its role with the relevant permissions.
• Group - several users connected by a common role.
• Role - a number of scopes for a particular user or a group.
• Scopes - granular permissions to do something in the system.

Viewing the organization dashboard

To view your organization dashboard, select the Organization option in the left pane.

Configuring two-factor authentication policy

You can require all your organization's users to use two-factor authentication (2FA). Before applying this policy, we recommend giving your users prior notice so that they have time to enable 2FA for their accounts.

To apply 2FA to user accounts, select the relevant checkbox in the ORGANIZATION SETTINGS section.

An administrator can see the 2FA status of each user in the organization in the MEMBERS section.

📘

Note

An organization-wide 2FA policy cannot be set to mandatory until all the administrative users have set up their own 2FA.
When enabling an organization-wide 2FA policy, the users can access their accounts only after they perform 2FA. In this case, an email notification is automatically sent to each affected user.

Defining hosts authorized for scanning

As a precaution, Bright only allows to scan trusted or authorized hosts.

To add a target host to the list of authorized hosts, follow these steps:

1. Download the .nex file from your Bright organization. For that, click the .nex link at the bottom of the ORGANIZATION SETTINGS section.

2. Add the downloaded .nex file to your application root directory.
   Once added, the .nex file enables Bright to recognize the application, associate it with your organization, and gives Bright permission to scan the target directly, without the need for the Repeater.

📘

Note

• Make sure that the server can serve this file from the webroot (top directory level or just / path) along with the other static resources from that location.
• You can always contact our support team at [email protected] or in the Intercom chart (on the bottom right of your screen) for help in authorizing hosts.

You can reuse this file as many times as needed.

Viewing your organization plan

The organization PLAN DETAILS section displays information about your Bright account, for example, total storage for your organization, number of engines, and the plan expiration date.

Manage organization API authentication tokens

You will need an authentication token (API key) to enable some Bright operations and integrations. You can create a user API key on your User Settings page. On the Organization page, you can obtain and manage authentication tokens (API keys) to access the Bright API.

To learn more about creating a user API key, see this article.