- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Apr 03, 2024 01:23 PM
Hi,
When we originally set up our Airtable SSO integration, it was set to match against the user primary identifier (we call it a netid) instead of using the email field. Let's say my netid is d39562b. When I log in with SSO, my account email address looks like: d39562b@dartmouth.edu.
However, if I don't have an Airtable account, and someone sends me an invite to join a base or workspace, the email goes to the email address which is my "real" one - joseph.montibello@dartmouth.edu. Then if I accept the invite, my account email address will be that form (joseph.montibello@dartmouth.edu). If there's no existing account with that form, it will create an account for that.
So my problem is twofold:
- When a user gets invited to a base or workspace, Airtable sends email to an address (firstname.lastname@dartmouth.edu) which will not match the data that our SSO endpoint is providing.
- Whenever an existing user (with a netid@dartmouth.edu address) gets an invite to a new base, they get a new account created. Then I have to look at what they have access to in that account, add that access to the appropriate netid@dartmouth.edu account, and remove the new (firstname.lastname@dartmouth.edu) account.
Not only do users end up with two separate accounts (and different access to bases for each of them), but both accounts are often billable, so we pay extra for the separate accounts.
I'm quite sure I'm doing something wrong here, but I don't know what it is. Is there some way to convince Airtable to only send email out to netid@dartmouth.edu style email addresses? Or is there some other way to solve this?
Thanks for any thoughts or suggestions you might have. Take care,
Joe Montibello
