Invite your coworkers

Writing an intro email?

If you want to introduce Robin before sending invites, we have an email template that makes explaining easy.

Robin is made for teams. Once you've created your organization, invite your coworkers to join you. There are a few ways to do this, and this guide will show the basic invitation email method.

You may be able to skip the basic invitation email method by enabling single sign-on through Google, Office 365, or custom SAML 2.0 instead. If you need to whitelist an entire domain (e.g. "Allow anyone with emails to join automatically"), you should use one of these SSO options.

Requires admin powers

You must be an account Owner or Admin to invite others to your account. Read more about member roles here.

Sending invitations

To invite people to your organization via email, follow these steps: 

Log into the web dashboard and visit Manage > People.
Click Invite new members, then enter the email addresses of the people you'd like to invite. Click the "+" to add team members individually, or upload a csv file containing email addresses to send invitations in bulk.
Next, decide how users will log in to Robin. If you want users to login via a username/password select Send invite. This automatically sends an email with a link to set up a Robin user account.
If you prefer users to log in via single sign-on select Add without invitations to avoid sending out an automated email invite from Robin. This route is ideal for premier customers who need to configure user groups and permissions before inviting the team to use Robin.  



The invite email

When you click Send Invitation, an email invite goes out to everyone on your list. Co-workers should keep an eye out for an invite email from <> that looks something like this:

Subject: You are invited to join {your team} on Robin


* Warning: we've seen the email invite get stuck in folks spam/junk folder from time to time.

When they click on the link, Robin will walk them through account creation and automatically add them to your organization.

Did this article help?