should I create a specific employee for creating a token for the REST api? It has no associated email since it is not a real person, can I create a user without an email?

AI generated answer (using internal Slack threads):

Based on the conversations, it is recommended to create a specific employee for creating a token for the REST API. This is often referred to as a "Service Account". This account is not tied to a real person but is used for integrations. However, it's important to note that even though this is not a real person, an email address is still required for the employee record. You can use a no-reply email or any other email that is not associated with a real person. The role associated with this account should be a web-services only role. This ensures that the account can't access anything through the front end. Remember, the access tokens are generated at the user level, so it's important to have an employee record to generate an access token. Also, it's a good practice to limit the permissions of the token to what is necessary for the integration. You can do this by customizing the role associated with the service account. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******