More often than not, this is purely a propagation issue that needs to be given more time than normal. This may be because of an issue on the back-end whilst communicating with GSuite. To be sure that the signature has failed, check your CloudManager Logs in the left hand panel - if you can see an error message for the affected user mentioning signature then it has indeed failed. If you cannot understand the error message please get in contact with our support team. If there is no error message and a lot of time has passed, be sure to check that the email address affected is the primary email address, check that they’re also part of the OU that’s being changed, and finally make sure that they have email signature enabled for the OU in question, if it’s not inheriting. If it is inheriting, ensure it’s enabled at the parent OU.
Our email signature system currently only updates the primary email address, there is no ability to push this through for all send as addresses in your GSuite account.
CloudManager does indeed support 2FA. We offer several methods for 2FA currently, including Google Authenticator, Ubikeys, Backup codes, and Fallback email addresses.
We advise against having both of these setup, IF you have SSO enabled for your domain.
First of all, ensure that your 2FA is enabled in the Global Settings on the Login tab. Next, make sure 2FA is enabled in GSuite as well if you’ve SSO. And finally, make sure that 2FA is set to be mandatory.
All items specified are whitelisted i.e. these are the only acceptable locations.
Absolutely, just be sure to enable all networks and related countries on both. If they’re not enabled on one side, users could potentially be blocked from logging in.
As well as the OU rules, you’ll need to navigate to the global settings and enable time/location restrictions from the login tab and update your settings.
This simply states that if a user is outside of the IP range or Country specified then they’ll be asked for 2FA, IF it is enabled on their account. Should they provide a correct code they’ll login, otherwise, they’ll be blocked out. If they don’t have 2FA setup then they’ll just be blocked.
CloudManager has only 1 domain administrator. However, it can have multiple administrators. CloudManager will provide, by default, an admin role to any user with an admin role in GSuite. However, if you wish for a more personalized admin role then you'll want to look into creating a custom role. Therefore to add another administrator to CloudManager, you can give a user admin privileges on GSuite or make your own role and assign that to them.
Before CloudManager can be used, an initial sync needs to be performed to gather data to populate the environment. Providing you've a super admin who hasn't changed in the middle of installation, they should be able to go back into CloudManager, confirm all initial details have been provided, and allow the start of the initial sync. If the above has been done, please be sure to get in contact with our support team.
Yes. When you first install CloudManager, you'll be given a free 30 day trail of our Premium Feature set. All the features that CloudManager offers are open for you to test.