‎Channel Permissions for Major Social Channels (Advocacy)

Channel Permissions for Major Social Channels (Advocacy)

Updated

3 months ago

Channel permissions are the initial set of permissions that a user must provide to each social channel for which they want to connect their accounts into Sprinklr Advocacy. Each Social Channel has a different set of permissions that they request from user.

Importance

The permissions are required for the proper functioning of the platform and are not recommended to be customized except few permissions for LinkedIn

Below is a detailed summary of permissions we ask for from different social networks while connecting them to the Sprinklr Advocacy site.

LinkedIn

Permissions	Permission Sprinklr use	Reasoning
Ability to Retrieve Organization posts, comments, reactions, and other Engagement Data	Yes	This is used for reporting purposes, but we only fetch posts posted from the Advocacy platform (Optional and only used if a user is connecting their company account)
Ability to Create posts on your organization's behalf	Yes	We use LinkedIn APIs to post content on LinkedIn and react to LinkedIn brand posts but not to comment on posts or delete posts. If we don't use this permission, then we won't be able to post content from Advocacy (Optional and only used if a user is connecting their company account)
Ability to modify, and delete posts, comments, and reactions on your organization's behalf	No
Ability to use basic profile information including name, photo, headline and public profile URL	Yes	We use profile Information to create social profile of a user
Ability to use primary email address associated with LinkedIn account	Yes	We use this to populate the email field in Community User
Ability to retrieve posts, comments, reactions and other engagement data	Yes	This is used for reporting purposes, but we only fetch comments, and reactions on posts that are posted from the advocacy platform
Use your 1st-degree connections' data	Yes	We use this the get the number of connections
Create modify and delete comments and reactions on posts on your behalf	No
Ability to create posts	Yes	We use LinkedIn APIs to post content on LinkedIn. If we don't use this permission, then we won't be able to post content from Advocacy.
Modify and delete posts, comments and reactions on your behalf	No
Retrieve comments, reactions and other Engagement Data on your organization’s posts	No
Ability to Manage Organization pages and retrieve reporting Data	No
Create, modify, and delete comments, and reactions on your organization's posts	No

Twitter

Permissions	Permission Sprinklr use	Reasoning
Ability to see tweets from user's timeline (including protected tweets) as well as your list and collections	Yes	We can get all the tweets, but we only use tweets posted from advocacy portal for the reporting purposes
Ability to see twitter profile information and account settings	Yes	We use profile information to create social profile of a user
Ability to Post tweets	Yes	We use Twitter APIs to post content on Twitter. If we don't use this permission, then we won't be able to post content from advocacy
Ability to Delete tweets	No
Engage with Tweets posted by others (Like, un-Like, or reply to a Tweet, Retweet, etc.) for you.	Yes	We allow users to like brand posts published from brand handles on native directly from the platform.
See accounts you follow, mute, and block.	No
Follow and unfollow accounts for you.	No
Update your profile and account settings.	No
Create, manage, and delete Lists and collections for you.	No
Mute, block, and report accounts for you.	No

Facebook

Permissions	Permission Sprinklr use	Reasoning
Ability to fetch name and profile picture from the account	Yes	We use profile Information to create social profile of a user
Email Address	Yes	We use this to populate the email field in Community User
Fetching Videos	No
Ability to get Page Likes	Yes	This is used for the reporting purposes
Current City/Town of the user.	No
Ability to create posts on user's behalf	No
Ability to modify and delete posts, comments and reactions on user's behalf.	No
Ability to create posts on Facebook page's behalf	Yes	We use APIs to post content on Facebook Page. If we don't use this permission, then we won't be able to post content on Facebook page from advocacy
Ability to modify and delete posts, comments and reactions on Facebook page's behalf for the page which is connected to Advocacy.	No
Ability to retrieve posts, comments, reactions and other engagement data on Facebook page which is connected to advocacy	Yes	This is a special case where brands wanted to report on stats on Facebook page connected on advocacy
Manage accounts, settings and webhooks for a Page.	No

Instagram (profile)

Permissions	Permission Sprinklr use	Reasoning
Username	Yes	We use profile Information to create social profile of a user
Account Type	Yes	We use profile Information to create social profile of a user

Instagram (business)

Permissions	Permission Sprinklr use	Reasoning
Username	Yes	We use profile Information to create social profile of a user
Account Type	Yes	We use profile Information to create social profile of a user
Ability to retrieve posts, comments, reactions and other engagement data	Yes	This is a special case where brands wanted to report on stats on influencer's business account
Ability to create posts on Instagram business account on user's behalf	Yes
Ability to modify and delete posts, comments and reactions on Instagram business account on user's behalf	No