Manage Users

Manage who can get access to your Assuredly account.

Provide access to internal people, consultants, auditors, suppliers and/or clients or third parties who you wish to have access to your account.

Types of Roles

There are four roles within the Assuredly platform:

1. Administrator
2. User
3. Assessment Contributor
4. Report Viewer

When a person is assigned one of these roles they get the following access:

Create a New User

To create a new user within your organisation or your Client's organisation.

1. Go to Home/Company/Team
2. Select add New Team Member
3. Add their Name, Job Title, Email, Phone

‍Tips:

1) Email address must be a corporate Microsoft or Google account.

2) Email addresses are case sensitive.

‍If you are providing your client access to Assuredly your company will need to have an enterprise agreement in place with Assuredly and your client will need to accept the end user license agreement when signing in.

Adding details

Notify Users When They are Added to an Account

Select whether you want Users to be notified about being added to the account by Notifying Users When They are Added to an Account

Disabling or Removing access

1. Select Remove on the user that you want removed from the Team
2. Select Disable on the user you want to remove access

‍

Managing Assessment Contributor and Report Viewer Access

• Once a person has been given access to an Assessment or a Report they will appear in the Team User view.
• When you view one of these roles you will be able to see which assessments or which reports they have access to and amend access to these from the Teams page.
• Tip: You can also remove someone's access from the share feature in the specific Assessment or Report they have been given access to

Having trouble with a user logging in?

When you create an email address in Microsoft 365 with capital letters it will revert the email address to lower case.  Various email systems decide how to treat capitalisation, grammar and punctuation.  As we leverage your authentication system to verify your user access the email address used to log in must match the authentication system.  

If you see this message it means that the users details cannot be corrected in the Assuredly platform but only by the user themselves or in the organisations user account system.

This user is linked to a Google of Microsoft Account.  For security purposes, their contact details can only be updated by: - <name> themselves - The administrator of the account within the Google or Microsoft service.

Has a user asked you to update their email address because they can't log in?

If a user attempts to use a capitalised or otherwise formatted version of their email address we will recognise them and let them know they need to ask their administrator to update their email address under Company/Team to the correct email address.  If they have never logged in before then the user account is unclaimed.  While the user account is unclaimed the administrator of the account can update their email address.

FAQS

Why can a I send an email to an email address but Ineed it to be in different capitalisation in Assuredly?

• Major providers like Gmail and Outlook ignore capitalization completely, routing all variants to the same exact inbox.
• Mail systems were designed to forgive accidental shifts or caps locks so messages do not bounce back. 

Can I access Assuredly with incorrect capitalisation?

• Yes, we allow any email address to be used tocreate an account of access the platform (authorisation) but when it comes to authenticationto an organisation the correct capitalisation must be in place. 

Why do I need to create Assuredly account in correct capitalisation?

• Attackers cycle through different uppercase and lowercase combinations of single email address (e.g., attacker@gmail.com,Attacker@gmail.com) to spam referral programs, bypass registration rate limits, or farm sign-up bonuses repeatedly on platforms that fail to sanitize inputs.
• We are looking into normalising all email accountsentered on client side  to lowercase toprevent this from happening in the next release.