How do you usually organize Employee records/Roles/Integrations and Access Tokens for external integrations? Let's say I am developing the app MyApp that calls a restlet using TBA. Would you create an integration called MyApp, an Employee called MyApp, a Role called MyApp and an access token for user/role/app MyApp. Or do you reuse all of these so you have a MyCompany app/employee/role/access token that is used by all of your custom integrations?

Hey @Gabriel Falkenberg - you would definitely want to setup a "Service Account" with the associated role. Keep it generic for all future use... planning for the future - just in case you get hit by a turnip truck. 😉 So yes - it needs a role with proper permissions (it's a lengthy process) And yes - Access Tokens are generated at the user level. Generic is the best way to go. Best.

Thanks @John ORourke! When you say

Service Account

, do you mean an Employee record that I use just for integrations or something else? I did find a post on reddit (searching for Service account!) that asks a similar question to mine and where the answer seem to be that there are no downsides to having a single integration user.

Correct @Gabriel Falkenberg an Employee/Service Account being the same thing... just a generic account. (In the old Microsoft days, the applications run as "services", we we would just create a generic user (service account) that would actually run everything behind the scenes. And the associated Roles can be customized, like having their password not expire.