Howdy @Scott Baldwin !

Yep, I think there’s an option that may work depending on your use case. The first solution I found is more intended for inviting colleagues to inSided rather than general users, but it might still be helpful.

There’s also options that can be used for inviting users in general. This guide seems to be the closest one I’ve found so far. The feature that makes this work might not have been enabled everywhere yet, but inSided might be able to flip the switch for you on request.

I think you can then make use of Integrations or the inSided APIs to automatically grant roles to new members who join and optionally add specific criteria to apply more granular controls over who gets what. I think inSided are using either Zapier or Salesforce on the inSpired Community to automatically grant a “verified customer” role to users who are known to be an inSided customer, so you can probably do something similar too.

I hope this helps with what you’re after.

Also, if you’re using token SSO, it's possible to set a custom role as part of the authentication process. 

@Blastoise186 thanks for chiming in. For our internal team we’ve been using the first option and also have SSO setup and auto-set the custom role at that point so we’re good there. We’re also working to enable customers to SSO and automatically have their role set but this might not complete before our beta and launch.

My use case here initially is inviting a group of users to our closed customer beta pre-launch. What I want to be able to do is to add them in-bulk, for some set their custom role to be “customer” for some and for others to leave them as “registered users”. It looks like I can only have the email and name, not their role in the system to start (primary and custom roles) -- which would speed things up tremendously when importing customers.

The API is an option we can look at but will require engineering resources and as such I was more interested in ways to do this when creating the invite.