Permissions

The complete set of permissions the Birdie integration user (the account whose OAuth token Birdie uses) needs to run all Birdie functionality. Derived directly from every Salesforce API call Birdie's

---

System permission

• API Enabled

Object permissions + field-level security

Object	Access	Fields (read/write)
Case	Read, Create	Id, Subject, Description, Origin
Case Comment (CaseComment)	Read, Create	ParentId, CommentBody, IsPublished
Email Message (EmailMessage)	Read, Create	ParentId, FromName, FromAddress, ToAddress, Subject, TextBody, HtmlBody, MessageDate, Status, Incoming
User	Read	Id, Name, Email, TimeZoneSidKey
User Role (UserRole)	Read	Name
Messaging Session (MessagingSession)	Read	Id, CaseId, Status, MessagingEndUserId
Contact	Read	Email
Routing Field (optional)	Read	<Some_Field>__c (will be the value of the storage-routing field if configured)
sfbirdiecx__Birdie_Recording__c (managed)	Read, Edit	LinkUrl__c, FirstViewedAt__c, LastViewedAt__c, AnonymousViewCount__c, FirstAnonymousViewedAt__c, LastAnonymousViewedAt__c, BirdieAuthViewCount__c, FirstBirdieAuthViewedAt__c, LastBirdieAuthViewedAt__c

Record visibility (sharing)

• View All on Case, Contact, and Account — so the integration user can act on records regardless of owner/sharing.

Messaging

• Permission to send messaging notifications via the standard sendConversationMessages action (Messaging enabled + send allowed).

Connected App OAuth scopes

api · refresh_token · web · id · openid · profile · email · chatter_api

---

This is the full union of what Birdie uses. It deliberately excludes Modify All Data, System Administrator, Setup/admin permissions, Apex authoring, Delete on any object, and any object not listed above.