OAuth scopes used for service integrations
JEMH Cloud can be integrated with third-party services to provide enhanced functionality. This integration is typically authorized by using the OAuth open standard mechanism.
OAuth scopes limit an apps access to a users account. When configuring an integration between JEMH Cloud and a third-party service, the user will be shown a consent screen from that service so that the permissions the scope grants can be reviewed.
Services
Google (SMTP, POP, IMAP)
Integration direction | Scope code/URL | Description |
---|---|---|
Inbound and outbound |
| Full access to the account (message read, write, delete) |
Inbound and outbound |
| View email address of account |
Microsoft 365 (Graph)
Integration direction | Scope code/URL | Description |
---|---|---|
Inbound and outbound |
| Grants app access to resources on behalf of the user for an extended time |
Inbound and outbound |
| Read the profile of the signed-in user |
Inbound |
| Create, read, update, and delete email in user mailboxes |
Outbound |
| Send email as user |
Slack
Integration direction | Scope code/URL | Description |
---|---|---|
Outbound |
| Allows application to confirm user identity |
Outbound |
| View basic information about public channels in a workspace |
Outbound |
| View basic information about private channels that the slack app has been added to |
Outbound |
| Send messages as the slack app |
Legacy services
Microsoft (EWS)
Integration direction | Scope code | Description |
---|---|---|
Inbound |
| Create, read, update, and delete email in user mailboxes |
Outbound |
| Send email as user |