Authorising SwipedOn Access

As an account administrator, you will need to follow some initial steps to grant permissions and enable SwipedOn to connect and enable users within your organisation to access SwipedOn.

  • Step 1: Create Admin group

Before you can approve the link between SwipedOn and Exchange you will need to create groups within Active Directory to define who is a system admin.

This is covered in the following article:

How to Create Administrator Active Directory group to access the admin portal

  • Step 2: Login

Navigate to the SwipedOn administration portal here

Enter your Office365 Administration Email Address.
Your administration email address may be different from your normal Office365 email address.


> Select the sign-in button.
> Select the Microsoft button for authentication if it displays.

  • Step 3: Authenticate

The Microsoft authentication sign-in page will display. Confirm your administration email address and enter the administration email account password.

  • Step 4: Accept permissions

The SwipedOnOnline permissions page will display. Select the ‘Accept’ button.
Note: This step may not display if you have previously logged into the SwipedOn Web Admin Panel.

  • Step 5: Connect to Exchange

Your SwipedOn company homepage will display.

You will need grant permission consent for the SwipedOn app to allow users from your company to use SwipedOn.

Select the ‘Sign in and grant permission’ button.

  • Step 6: Accept permissions

The SwipedOnNative permissions page will display. Select the ‘Accept’ button.
You will be redirected back to the portal homepage.


Below is a list of the permissions you are consenting for SwipedOn to access and a description of the permissions, as well as why they are needed.

Read directory data

Allows the app to read data in your company or school directory, such as users, groups, and apps.

Why is this needed? This permission is used to read Active Directory groups and check the users of those groups to ensure they have permission to perform the functions.

Read all groups

Allows the app to read basic group properties and memberships on behalf of the signed-in user.

Why is this needed? This permission is used to read Active Directory groups and check the users of those groups to ensure they have permission to perform the functions as a signed in user.

Read all users' basic profiles

Allows the app to read a basic set of profile properties of all users in your company or school on behalf of the signed-in user. Includes display name, first and last name, photo, and email address. Additionally, this allows the app to read basic info about the signed-in user's reports and manager.

Why is this needed? This permission enables to capture of the users name and photo to display in the app for the account settings and find a colleague features.

Sign in and read user profile

Allows users to sign in to the app, and allows the app to read the profile of signed-in users. It also allow the app to read basic company information of signed-in users.

Why is this needed? This permission enables to capture of the users name and photo to display in the app for the account settings and find a colleague features as a signed-in user.

If you agree, this app will be granted the specified application permission(s) to resources belonging to all users in your organization, and delegated permission(s) to resources belonging to the signed-in user.

Did this answer your question?