🧑‍🤝‍🧑User Organisations

Group users into Organisations to specify how they should access Realpad

Story 1: The majority of users are your direct internal employees, with the company's corporate email. Ideally, you want your team to access Realpad only via the email you have control over. For that purpose, you can set up a new Organisation, which limits access methods to emails matching your email domain - @mydevelopment.com.

Story 2: Your organisation requires certain security compliance (2FA), which is provided by the security configuration of Microsoft accounts. For that purpose, you can create the Organisation and limit the access to Microsoft SSO - this way, for users of this Organisation the only path to access Realpad would lay through logging into users' Microsoft accounts.

Set up an Organisation

Keep in mind:

1. Each user belongs to one Organisation.

2. You can't delete an Organisation with users in it.

3. Correspondingly, you must have at least one Organisation configured.

To make sure some users have access to Realpad only via their corporate Microsoft account you have to create an Organisation with corresponding access methods, and then add specific users to it. After adding users to the organisation, they will be asked to provide the correct authentication details to continue to use Realpad.

This is how the process looks like schematically.

As Admin, you have to Create a new Organisation & Invite users. This will take just a few clicks, in the demo below you will:

1. Locate Organisations in Realpad

2. Create a new Organisation

3. Setup a new Organisation

4. Find users to be invited to the new Organisation

5. Invite all selected users

There are a few reasons to consider keeping Login & Password access method for users. For example, users of Tablet app and Integration accounts won't be able to access Realpad without Login & Password (yet).

If Organisation changes don't require more info from users, they won't be even bothered. Otherwise, as a User, you will have to set up new credentials under your new Organisation next time you log in.

FAQ

What access limitations can I achieve using Organisations?

Setting up an Organisation allows you to easily control access to the system by specifying:

• method of authentication (Microsoft SSO, Login & Password)

• email domain (example: only @mydevelopment.com users)

Who can change the Organisation for users?

Only Admins can change the Organisation for users. All users can see the Organisation they belong to in user details.

How many organisations can I have?

You can have as many organisations and users inside as you want.

Is Google SSO coming?

Let us know if that's something you need in the form below.

Something else?

We are doing our best to prioritise the most impactful feedback, tell us where to start!