Help
HomeFeaturesPricingBlog
  • What is Keeping?
  • Getting Started
    • Quick start for admins
    • Quick start for agents
    • Using Keeping in Gmail
    • Keeping and your customer
    • Keeping for Chrome
    • Keeping for Safari
  • Fundamentals
    • Mobile & web access
    • Converting an email to a ticket
    • Using Templates
    • Changing ticket status
    • Assigning a ticket
    • Editing ticket recipients
    • Moving a ticket
    • Sharing a ticket
    • Using tags
    • Enable an autoreply
    • Creating a new ticket
    • Collision detection
    • Email signatures
    • Private notes
    • Activity log
    • Managing spam
    • Shared drafts
    • Agent Availability
  • Setup
    • Installing the Chrome Extension
    • Installing the Safari Extension
    • Integrations
      • Asana
      • ClickUp
      • HubSpot
      • Jira
      • Linear
      • Shortcut
      • Shopify
      • Zapier
    • Connecting a mailbox
      • Sign in with Google
      • Connect a Google Group
      • Connect a Gmail Alias
      • Forwarding your mailbox
      • Custom domains
      • Connect a web form
      • Disconnecting a mailbox
    • Inviting users
    • Admin & agent roles
    • Manually updating the Extension
  • Workflows
    • What are Workflows?
    • Creating Workflows
    • Workflow conditions
    • Workflow actions
    • Round Robin assignment
  • Service Level Agreements
    • What are SLAs?
    • Creating an SLA
    • SLA conditions
    • SLA actions
  • Satisfaction Ratings (CSAT)
    • What are CSAT Ratings?
    • Enabling Satisfaction Ratings
    • Customizing the CSAT widget
    • CSAT Reports
  • Reporting & Analytics
    • What are Reports?
    • Classic Reports
      • Setting work schedules
      • First response time
    • Advanced Reports
      • Team performance
      • Agent performance
      • Ticket statistics
      • Message statistics
      • Export to CSV
  • Preferences
    • Reversing conversation order
    • Pushing tickets into inbox
    • Hiding the Keeping toolbar
    • Close & Next
    • Personal Inbox Signature
    • Notifications
      • Desktop Notifications
      • Browser permissions
      • Inside Gmail
    • Set your business hours
  • Account & Plans
    • Adding and removing paid seats
    • Changing billing plans
    • Changing organization name
    • Updating your billing information
    • Pausing your subscription
    • Cancelling your subscription
  • Troubleshooting & FAQs
    • Toolbar Not Refreshing
  • Security and Privacy
    • Security & Privacy Practices
    • Google Permissions
Powered by GitBook
On this page
  • Why does Keeping need permission to my Gmail account?
  • Description of the permission used
  1. Security and Privacy

Google Permissions

Learn about the permission Keeping needs to sync support email to your account.

PreviousSecurity & Privacy Practices

Last updated 3 years ago

Why does Keeping need permission to my Gmail account?

Keeping provides shared mailbox functionality built on top of Gmail. Shared Mailboxes are a way to manage shared email very easily right from Gmail. When a new email comes to a shared mailbox, this email is shared with everyone who is part of the shared mailbox.

Keeping uses the Gmail API to fetch an email from the source Gmail account and then push this email to all the recipients who are part of the shared mailbox. The section below describes how the following scopes are used by Keeping to provide the shared mailbox functionality.

Google audits Keeping on an annual basis to ensure we are using these permissions correctly.

Description of the permission used

To insert email into the Gmail accounts which are part of the Shared Mailbox. When an email needs to be copied to a Gmail account, insert is required.

Keeping may add or remove dedicated Gmail labels to sort your Keeping tickets.

To modify the labels (user labels and system labels) in an email or a conversation. This allows Keeping to move emails from one label to another and provide a workflow for the user.

To get the email headers and the email body. Keeping looks at the email headers to identify emails that need to be shared. If sharing is required, the email is downloaded as an encrypted blob on our server, then pushed into the Gmail accounts it needs to be shared with.

To send an automated response for the emails in the Keeping shared mailbox.

gmail.insert
gmail.labels
gmail.modify
gmail.readonly
gmail.send