Teams provide a way for you to group Users, API keys, and Targets in one place so that managing them becomes easier and time-efficient. You can create multiple teams for one account. Teams act as independent units/groups and help you separate and assign targets for each team, limit the number of targets, set scopes, and user roles.

Learn how Teams can help your organization.

Adding a team with/without a target quota

Follow these steps to add a Team:

  1. Log in to your account and choose Teams from the side menu.

  2. Click Add team and give it a name; this is required to identify the team.

  3. Optionally, you can limit the number of targets each team can create by assigning a target quota; this value depends on how many targets can still be added to your Probely account.

  4. If you assign a target quota (a limit of targets), you can reserve target slots for the current team. Doing so prevents other teams from using those slots beforehand. Just like defining a target quota, reserving that quota to the team is optional.

Note that one user can be added to different teams and assigned to roles that don't affect one another, such as an admin or developer.

Managing a team

When you access a team's details, you have 3 tabs where you can manage that team: Users, API Keys, and Targets; the Users tab is selected by default.

To manage a team, go to its details and:

  • From the Users tab, add users in bulk and assign them a role in the context of that team.

  • Click on the API Keys tab, and manage API Keys precisely as you did for users.

  • Go to the Targets tab, and add targets to the team by selecting the desired ones from the list of existing targets.

Once you have your team created and set up, users that were added to that team will be able to access the respective targets with the role you defined.

Managing Users/API Keys/Targets

Similar to how you can manage every component of the Team (Users/API Keys/Targets) from the team's details, you can also manage these components from their respective sections.

For instance, through the Users list, you can add new or edit existing users to accommodate different access scopes:

  • A role for the Global (account) scope, the user can use that role for the entire account.

  • A role for a specific Team, the user can use that role in the context of that team only.

  • A role for a specific Target, the user can use that role only in the context of the selected target.

To do this, select the role you want to assign and choose the respective scope using the Teams/Targets toggle and selecting the intended scope from the respective dropdown.

You can do precisely the same for API Keys by accessing the new menu entry API Keys and either adding a new API Key or editing an existing one.

Just like for Users and API Keys, you can also define a specific target’s scope by adding a new target or editing an existing one. Suppose you assign a target to a team. In that case, members of that team can access it. Depending on the role they have in the context of that team, what they can do on the target may vary.

Suppose the target is bound to the account / global level. In that case, only users with a Global role can list/view/change or otherwise interact with that target. Depending on their role in a global/account context, what they can do on the target may vary.

  • A user with Global (account) access can access all targets

  • A user with access to a specific team can only access targets that belong to that team

Note that a target can only belong to a team at once.

Suppose a specific target belongs to a team, and you need to allow a user to access that target but don’t want to give them access to every target from that team. In that case, you can always assign a target-specific role to that user, going to the Users list, as explained above.

Managing Scanning Agents

Finally, you can manage scanning agents based on your organization’s requirements.

  • You can set a scanning agent to be used freely for the account, regardless of the scope of the target. Therefore, the scanning agent’s scope is not restricted.

  • Alternatively, you can restrict a scanning agent to one or more teams. Therefore, only targets that belong to those teams can use the scanning agent.

Did this answer your question?