About Teams
What are Teams?
A Team brings together users to share related logins, notes, cards and identities securely.
Bravura Safe Teams allow owners/admins/members to:
Share safe data securely with others.
Manage related users for any group of people that needs to share data securely.
Relate users and items together via Collections to share logins, notes, cards and identities securely.
Manage each Team's unique safe, including its items, members, policies and settings.
Based on your business requirements, a Team could be one of the following:
Organization
Company
Division
Geographic region
Project team
and more...see Common Team uses
Team items are found in members' My Safe view alongside 'personal' work items. Members can also access Team items from the Teams view. Filters group items for assigned Collections in the same way that folders organize personal items.
Enterprise and Regular Teams
There are two types of Teams:
Enterprise (global)
Regular
Enterprise Teams
Enterprise Teams allow Bravura Safe administrators to configure global settings and polices that apply to ALL Teams and members:
Two-step login
Single Sign-on
Team policies:
Master password requirements
Master password reset
Remove individual vault (use Team safes only)
Remove Share
Share options
For the Enterprise Team only:
Team information
Password generator requirements
Import and export Team data
Enterprise Teams allow members to manage Enterprise options:
Enroll in password reset
Open the Bravura OneAuth device manager to manage paired devices
See Enterprise (global) Team settings for more information.
Regular Teams
Regular Teams allow Team owners to configure Team-specific settings and policies:
Team information
Password generator requirements
Import and export Team data
See Regular Team settings for more information.
Creating enterprise and regular Teams
In a brand-new Bravura Safe environment, the Team created first is the enterprise Team; subsequent Teams default to the regular normal Team type.
Common Team uses
Any user can create a Team and invite others to join. Assemble Teams as needed. Common Team usage patterns:
Companies standardize policies and give a consistent experience, then allow users to expand their access as needed:
Company-wide federated applications (for example, HR and office solutions)
Company Policies
Company handbook references
Divisions allow members of divisions to access what they need quickly and easily:
Federated web applications useful for a division (for example, Salesforce and Zendesk)
Policy documents
Division handbook information
Departments allow departments to function efficiently and reduce calls for help:
Department handbook links
Links to just-in-time access portals
Software used within a department
Departmental information systems
Teams store information that allows a Team to function efficiently:
Secrets
Development/Test systems
Planning documents
Project management portals
Links to just-in-time access portals
Ad-hoc:
Sharing passport information between executives and executive assistants
Transferring credit card information between finance and an employee
Customers store information that allows you to service your customers:
Access credentials
RFP and project management portals
Ticketing systems
Within Teams, there are Collections. See Collections for more information.
When to create a Team
To determine if you need to create a new Team or use an existing one for an item, consider the following questions:
Is there an existing Team with the same owners and members you need?
If there is, that may be a good place for your item. If the existing Team has more members than you need to share the item with, you can further restrict the Team members that can see the item through a collection.
For example:
To share a social media login with only the owner of an existing Marketing Team, add the item to the Marketing Team and place it in a collection where only the Marketing owner and you are members. Other Marketing Team members cannot access the login information.
Are there any conflicting Team policies that would interfere with the item, or with the members attempting to access it?
If no conflicting policies exist with your item, the existing Team may work for your item. If there are conflicts, you may need to create a new Team.
For example:
If the Marketing Team has a password generator policy that requires generated passwords to be 16 characters long, and your marketing software login item has a maximum password length of 12 characters, create a new Team with a different policy and a collection for that login item.
Does adding the item to an existing Team/collection make sense? Will someone intuitively look for it there?
If users would naturally go to the existing Team to look for the item, it may be the right place for your item.
For example:
You want to share a credit card item with the CEO. The CEO and you are members of several Teams; for example, Legal, Human Resources and Training. Finding the credit card item in one of the existing Teams would not be intuitive.
In this case, create a new Team that follows the existing department structure, such as a Finance Team. The collection you create in that Team would only include yourself and the CEO as a member, so even if the Finance Team grows in members overall, the credit card item remains shared only between you.
The flowchart below can help you determine if an existing Team in Bravura Safe meets the criteria for sharing your item:
If you have determined a new Team is needed, follow product documentation considerations on how the Team should be named and configured.