ToogleBox Recall API scope usage

The following API scopes are activated at activation of ToogleBox Recall:

  • https://www.googleapis.com/auth/userinfo.email: Used in add-on to get the email address of the user.
  • https://www.googleapis.com/auth/userinfo.profile: Used to get the name of the user.
  • https://www.googleapis.com/auth/gmail.addons.current.message.readonly: Used by the Add-on to get sender and Gmail message_id of emails.
    The sender is needed to determine whether the email sender is the current user or not. The Recall button is displayed only if the sender is the current user.
    The Gmail message_id is passed to the ToogleBox backend service as retrieve argument to find and delete the email chosen by the current user to be recalled.
  • https://www.googleapis.com/auth/script.locale: Used to get the user language. It is used to interact with the user in their language.
  • https://www.googleapis.com/auth/script.external_request: Allows ToogleBoard to connect with ToogleBox and storage.googleapis.com to retrieve the notes to be displayed.
  • https://www.googleapis.com/auth/gmail.addons.execute: Used to execute ToogleBoard Gmail add-ons.

ToogleBoard API scope usage

The following API scopes are activated at activation of ToogleBoard:

  • https://www.googleapis.com/auth/userinfo.email: Used in add-on to get the email address of the user.
  • https://www.googleapis.com/auth/userinfo.profile: Used to get the name of the user.
  • https://www.googleapis.com/auth/script.locale: Used to get the user language. It is used to interact with the user in their language.
  • https://www.googleapis.com/auth/script.external_request: Allows ToogleBoard to connect with ToogleBox and storage.googleapis.com to retrieve the notes to be displayed.
  • https://www.googleapis.com/auth/gmail.addons.execute: Used to execute ToogleBoard Gmail add-ons.


ToogleBox API scope usage

The following API scopes are activated at activation of ToogleBox:

  • https://www.googleapis.com/auth/userinfo.email: Used in login to get the email address of the connecting user. ToogleBox uses the email to identify the user and to send results emails.
  • https://www.googleapis.com/auth/userinfo.profile: Used to get the name and profile photo of the connected user.
    • The user profile photo appears in the upper right of the screen. It is also used when applying signatures whose design include with profile pic.
    • The user name appears in the upper right of the screen and is used to personalize emails sent to them.
  • https://mail.google.com/: Used to find and delete unwanted emails within the user domains.
    • One of the main services we offer allows Superadmins and authorized users to delete unwanted or wrongful (phishing, hate mail, etc.) emails in all accounts within the domain in a matter of minutes.
    • Another service we offer is the email recall, where an end-user can recall within their domain an email they sent.
  • https://www.google.com/m8/feeds: Used to find and delete user contacts and shared contacts in the Directory. It is used in three services we offer:
    • Clean up contact: removal of unwanted contacts from end-user user address books.
    • Internal contact sync: it keeps internal contacts in sync with the Directory of G Suite by 1) deleting contacts corresponding to nonexistent accounts or groups, and 2) updating contacts corresponding to accounts whose name has changed. This sync prevents G Suite recipient autocomplete feature to display wrong names, ex-employees or nonexistent addresses.
    • Add external contacts to the Directory (as Shared contacts) through a csv file upload.
  • https://www.googleapis.com/auth/admin.directory.orgunit.readonly: All our services can be targeted to specific OUs. We use this scope to validate the OUs chosen by the user.
  • https://www.googleapis.com/auth/admin.directory.user: Used to retrieve and update end-user info in the Directory.
    • End-user info like first name, last name, telephone, etc. can be updated through our services. There is a batch update through a csv file upload and a one-by-one update dialog.
    • We also use the scope to get a list of users of the domain to run email deletion, contact deletion, signature enforcement, contact maintenance, etc.
  • https://www.googleapis.com/auth/admin.directory.userschema.readonly: Used to get user profile custom attributes’ category and field names. The service needs these names because these attributes are part of the user profile and as such need to be shown with a name.
  • https://www.googleapis.com/auth/admin.directory.group.readonly: Used to get email addresses within groups. Since the Recall service needs to know all recipients of the target email, we use this scope to know all recipients included in groups.
  • https://www.googleapis.com/auth/admin.directory.customer.readonly: Used to get the customer id of a user. This info is used to understand to which customer a user belongs.
  • https://www.googleapis.com/auth/admin.directory.domain.readonly: Used to get the list of domains of a customer. This info is used to understand which domains belong to each customer. This info is used during the initial service activation to display a list of all candidate domains of the customer.
  • https://www.googleapis.com/auth/gmail.settings.basic: Used to get and update user signatures. We offer a Signature Management service.
  • https://www.googleapis.com/auth/admin.directory.group: Used to create and maintain groups under Dynamic Group Schemas.
  • https://www.googleapis.com/auth/apps.groups.settings: Used to create and maintain settings of groups under Dynamic Group Schemas.