Set how people sign in

Steps

1. Step 1 of 10

   Open the company administration

   Authentication is in the company administration.

   Authentication is a page of the company administration, not of a workspace. In the console menu, click the workspace picker under the company name and choose Manage company (Norte SAS). The workspace menu is replaced by the company menu. You can also get there from the setup guide on My Bridge: Authentication is the second step of Company setup, and its Open button opens the page in a new window.

   • Workspace picker › Manage company
   • The company menu replaces the workspace menu
   • Or from My Bridge › Company setup

   Watch step 1 on the screen

2. Step 2 of 10

   Choose Authentication in the company menu

   Sign-in belongs to the company, not to a workspace.

   The company menu has one section, Company, with five pages: Company information, Usage and costs, Workspaces, Company members and Authentication. Choose Authentication, the last one. The band at the top, Company configuration · Norte, is a reminder that sign-in belongs to the company: each person has one identity and takes it into every workspace they can reach. That is why a change here reaches everybody, in every workspace, at their next sign-in.

   • Company › Authentication, the last page
   • One identity for every workspace
   • A change reaches everybody at their next sign-in

   Watch step 2 on the screen

3. Step 3 of 10

   Check the status of each method

   Each method shows its policy, its setup and its use.

   Sign-in methods shows four methods: Basic authentication, with an email address and a password; Sign in with Google; Sign in with Microsoft, with a work account; and Passwordless sign-in, with a single-use code sent to the email address. Each method shows separately its Policy (Allowed or Not allowed), its Setup (Configured, Connected, Not configured or Needs attention) and how many people sign in with it. Only a method that is allowed and set up works. In the example, Sign in with Microsoft is allowed but needs attention, with its card outlined in the warning colour: the consent given to Bridge expired, so nobody can use it until it is granted again.

   • Policy: Allowed or Not allowed
   • Setup: Configured, Connected, Not configured or Needs attention
   • It works only if allowed and set up

   Watch step 3 on the screen

4. Step 4 of 10

   Allow or withdraw a method

   The switch decides whether the company accepts the method.

   Each method has a switch on the right, with its state: Allowed or Not allowed. Turn it on so the company accepts that method, or off to withdraw it. The change waits in a draft: nothing saves on its own. Allowing a method does not set it up: a method that is allowed but not set up is no way in. In the example, you turn on Sign in with Google, which is still Not configured.

   • Allowed or Not allowed, on each card
   • It waits in a draft until you apply
   • Allowing does not set the method up

   Watch step 4 on the screen

5. Step 5 of 10

   Connect Google or Microsoft

   Google and Microsoft are connected with the provider.

   Sign in with Google and Sign in with Microsoft need a connection with the provider. Click Connect, or Reconnect when the method already had a connection, like Microsoft. Bridge asks you to confirm: you will be sent to the provider to sign in as an administrator and grant Bridge the access it needs. Bridge asks to read the name, the email address and the directory of that account, and it never receives the password. Click Continue.

   • Connect, or Reconnect if it had a connection
   • You sign in to the provider as an administrator
   • Bridge never receives the password

   Watch step 5 on the screen

6. Step 6 of 10

   Check the connection

   A new connection is a draft until you apply it.

   Once the provider confirms who granted access, the method’s Setup changes to Connected and its note says when and by whom it was connected. The Connected notice is a reminder that it is still a draft: the connection only becomes a way in once the method is allowed and you apply the changes. For Microsoft, Reconnect renews the expired consent, and the note names the verified domain it is restricted to.

   • Setup changes to Connected
   • The note says when and by whom
   • A way in once allowed and applied

   Watch step 6 on the screen

7. Step 7 of 10

   Validate people against your directory

   Validation decides who may exist in the company.

   Corporate validation holds Microsoft Entra ID validation. It checks every person who signs in against your organisation’s directory and reads the groups they belong to. It is not the Microsoft button on the sign-in screen: it decides who may exist in the company. Connect sends you to Microsoft to sign in as a directory administrator and choose the tenant the company is validated against. Before it decides who may sign in, the tenant has to be bound to a verified domain and the group rules have to be written. In the example it is Not allowed: nobody is checked against a directory.

   • Checks every person against the directory
   • Not the Microsoft button on the sign-in screen
   • First: a verified domain and group rules

   Watch step 7 on the screen

8. Step 8 of 10

   Verify your domains

   Only a verified domain can restrict a method.

   Verified domains lists your company’s domains with their status: Verified, Verification pending or Not verified. A method can only be restricted to a domain your company has proved it owns. The list of domains is kept in Company information; the ones you add there appear here as Not verified. Click Verify: the domain changes to Verification pending, “Waiting for the DNS record to appear”, and it is not verified until the DNS record is found. In the example, norte.co is verified and you verify norteadvisors.co.

   • Verified, Verification pending or Not verified
   • The list is kept in Company information
   • Verify waits for the DNS record

   Watch step 8 on the screen

9. Step 9 of 10

   Review the changes before applying them

   Before applying, you review what changes and who it reaches.

   The bar at the bottom shows Unsaved changes and how many methods work today with the draft, for example 3 methods work today. Discard goes back to what was saved. Review and apply opens Review the sign-in changes: What changes lists each change, for example that Sign in with Google becomes a way in for everybody and that verification starts for norteadvisors.co. After this is applied sums up which methods people can sign in with, which are not working today, whether directory validation is on and who the change reaches: every person in all 4 workspaces.

   • The bar shows unsaved changes
   • Review and apply shows what changes
   • Discard goes back to what was saved

   Watch step 9 on the screen

10. Step 10 of 10

    Apply all the changes at once

    The whole draft is applied, in one operation.

    Click Sign in again and apply. Bridge asks you to sign in again, applies the whole draft in one operation and keeps a record of who changed what. If the draft would leave nobody able to sign in, the alert says so and the button is disabled. When it is applied, the Sign-in methods applied notice confirms that everybody uses them from their next sign-in; sessions already open are not closed. Keep editing returns to the page without applying. Then continue with Workspaces, the next step of Company setup: the guide “Create and organize your workspaces” shows you how.

    • Sign in again and apply
    • Refused if nobody could sign in
    • Open sessions stay open

    Watch step 10 on the screen