Skip to main content

Choosing an onboarding method

You can choose to board regular users via:

Consider the following points to determine the method that suits your organization:

Number of users

  • How many users are going to be onboarded as initial product administrators?

    • Names of these users?

    • Names of the assigned client's product administrators with the ability to reach out to Bravura Security support?

    The client's initial product administrators may serve as the help desk for the client's general users. There may be several client product administrators that general users are allowed to reach out to for assistance, but only two of the client's product administrators are assigned the ability to reach out to Bravura Security support via support@bravurasecurity.com.

  • How many general users will be onboarded?

    The number of general users is relevant in determining the preferred onboarding method. In general:

    • General users < 100 = Manual onboarding

    • General users > 100 = Directory Connector

    • Onboarding via SSO is possible, but not recommended. It is possible to turn on SSO authentication later after general user onboarding.

Help-desk assistance

If help desk assistance will be available to regular users:

  • Who will they be?

    • Bravura Safe product administrators?

    • Separate group?

  • How will they be contacted?

    • Group email address?

    • Ticket submission?

  • How will general users be informed?

Are there enough help desk agents to assist the number of general users? Consider adding more help desk agents or alternative people to reach out to if it is estimated there will be more questions than they can handle.

Inform your general users how to reach out for Bravura Safe assistance. This should be included in a user presentation or email before general user onboarding so users know what is expected of them. If a help desk already exists for your company this may not require additional user education.

Team structure

For user engagement

  • Will all users be allowed to create Teams?

    Do they need to check for existing Teams for specific types of Teams being created? Example: creating Teams for existing customers.

  • Is there a specific way you want general users to name Teams?

    • By department?

    • By project?

  • Are there regular Teams that initial product administrators will create before general user onboarding? (e.g. Departmental Teams)

    These are good to include in general user education so staff are aware of the type of Teams that already exist

See About Teams for general information.

Note the following:

  • There is no limit on the number of Teams created.

  • Teams can be deleted if incorrectly created.

    They can only be delted by someone with privileges to use the https://<instance>/admin console. These users are identified by the client when the Bravura Safe instance is created by Bravura Security.

  • Regular users cannot see all available Teams.

    They can only see the Teams that they are confirmed members of. A business process can be implemented where general users are educated to ask an admin console user if a Team exists before they proceed in creating a new one.

Compatibility

  • Directory Connector synchronization is compatible with:

    • Active Directory

    • LDAP

    • Azure AD

    • GSuite

    • OneLogin

    • Okta

  • SSO providers include

    • Bravura Security Fabric

    • Azure

    • Okta

    • Google SAML

In this section: