{
  "Status": true,
  "Message": "",
  "Response": {
    "post": {
      "postuid": "m4e9vt2e0b",
      "tenantuid": "d8b744fc-2e70-4089-bb80-dd1d08f6c7b2",
      "projectuid": "239698c5-f7eb-4574-8cc8-c6568f08b3a0",
      "title": "Permissions",
      "slug": "article/m4e9vt2e0b-understanding-role-permissions-in-daily-story",
      "html": "\u003Cp\u003EDailyStory supports a robust permissions model used to control what users can do on the platform. An administrator of the account can create different permissions with limited access to certain features.\u003C/p\u003E\u003Ccite class=\u0022warning\u0022\u003E\u003Cspan class=\u0022title\u0022\u003EWarning\u003C/span\u003E\u003Cp\u003EEnabling permissions has immediate impact to users. We recommend approaching permissions with a plan for who should and should not have access.\u003C/p\u003E\u003C/cite\u003E\u003Ch2 id=\u0022read_before_turning_on_permissions\u0022\u003ERead before turning on permissions\u003C/h2\u003E\u003Cp\u003EBy default, permissions are \u0022off\u0027. With no permissions enabled, all users have full administrative rights.\u003C/p\u003E\u003Cp\u003EWhen a permission is created, permissions are \u0022on\u0022. When permissions are on, only the account owner has full administrative rights. All other users are given no rights unless that are granted.\u003C/p\u003E\u003Cp\u003EPermissions are granted by setting what the permissions ability is and adding users.\u003C/p\u003E\u003Cp\u003EWhoever is assigned as the site owner is always an administrative-level user independent of the permissions assigned to them.\u003C/p\u003E\u003Ch3 id=\u0022create_a_permission\u0022\u003ECreate a permission\u003C/h3\u003E\u003Cp\u003ETo add a permission, which will also enable permissions, click the \u003Ccode\u003EAdd Permission\u003C/code\u003E button, and name the permission.\u003C/p\u003E\u003Cimg class=\u0022lazy-load\u0022 data-width=\u0022633\u0022 data-height=\u0022249\u0022 data-src=\u0022https://graffiti-auf7e6dwhxhcbwek.z03.azurefd.net/d8b744fc-2e70-4089-bb80-dd1d08f6c7b2/239698c5-f7eb-4574-8cc8-c6568f08b3a0/b1e065a8f324a1f6d28962b0ead7965e.png\u0022 style=\u0022\u0022 alt=\u0022\u0022/\u003E\u003Ch3 id=\u0022grant_rights_and_add_users\u0022\u003EGrant rights and add users\u003C/h3\u003E\u003Cp\u003EOnce you create the permission, select the abilities granted and then add \u003Ca href=\u0022/article/7legytw1r5-daily-story-users\u0022\u003Eusers\u003C/a\u003E.\u003C/p\u003E\u003Cimg class=\u0022lazy-load\u0022 data-width=\u0022804\u0022 data-height=\u0022994\u0022 data-src=\u0022https://graffiti-auf7e6dwhxhcbwek.z03.azurefd.net/d8b744fc-2e70-4089-bb80-dd1d08f6c7b2/239698c5-f7eb-4574-8cc8-c6568f08b3a0/a9fc14bb5cb353a0fd8c4944b6d5ae84.png\u0022 style=\u0022\u0022 alt=\u0022\u0022/\u003E\u003Ch2 id=\u0022manage_permissions\u0022\u003EManage permissions\u003C/h2\u003E\u003Cp\u003ETo edit the name, abilities, and users associated with it, just click on the \u003Cb\u003EPermission Name\u003C/b\u003E from the \u003Cb\u003EManage Permissions\u003C/b\u003E page.\u003C/p\u003E\u003Cimg class=\u0022lazy-load\u0022 data-width=\u0022812\u0022 data-height=\u0022354\u0022 data-src=\u0022https://graffiti-auf7e6dwhxhcbwek.z03.azurefd.net/d8b744fc-2e70-4089-bb80-dd1d08f6c7b2/239698c5-f7eb-4574-8cc8-c6568f08b3a0/179ba6326145c8f517207429b7a8ee8a.png\u0022 style=\u0022\u0022 alt=\u0022\u0022/\u003E\u003Ch3 id=\u0022permission_abilities\u0022\u003EPermission Abilities\u003C/h3\u003E\u003Ccite class=\u0022recommended\u0022\u003E\u003Cspan class=\u0022title\u0022\u003ERecommended\u003C/span\u003E\u003Cp\u003ENote about the Administrator Permission: There is no limit to how many users can have this permission, and it grants access to the Account Settings section of your DailyStory application. Features (such as configuring permissions, adding users, enabling integrations, setting site options, creating API keys and more) are all restricted to the\u0026nbsp;Administrator\u0026nbsp;Permission.\u003C/p\u003E\u003C/cite\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EAbility\u003C/th\u003E\u003Cth\u003EDescription\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EAdministrator\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the administrator ability\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EAutomationCanManage\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view and manage (create, edit and delete) automations\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EAutomationCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view automations\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003ECampaignCanManage\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view and manage (create, edit and delete) campaigns\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003ECampaignCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view campaigns\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EContactCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view a contact\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EContactCanManage\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view and manage (create, edit and delete) contacts\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EContentCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view content\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EContentCanManage\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view and manage (create, edit and delete) content, including Conversations\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003ESegmentCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view segments.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003ESegmentCanManage\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view and manage (create, edit and delete) segments\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EEmailCanSend\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to send emails\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003ETextMessageCanSend\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to send text messages\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EPushCanSend\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to send push notifications\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003ETaskCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view tasks\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003ETaskCanManage\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to manage tasks\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EIntegrationCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view available integrations\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EIntegrationCanManage\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to enable and manage integrations\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003EReportCanView\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EGrants the ability to view reports\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Ch2 id=\u0022frequently_asked_questions\u0022\u003EFrequently Asked Questions\u003C/h2\u003E\u003Cp\u003EBelow are some frequently asked questions about permissions.\u003C/p\u003E\u003Csection class=\u0022faq\u0022\u003E\u003Ch3\u003EA user is in two roles, which role grants their permissions?\u003C/h3\u003E\u003Carticle\u003E\u003Cp\u003EDailyStory is designed to grant the highest level of permission given by the roles a user belongs to. If a user is in multiple roles and the first role does not grant a permission, e.g.\u0026nbsp;\u003Ccode\u003ECampaignCanManage\u003C/code\u003E, but the second role does grant it, the user is given\u0026nbsp;\u003Ccode\u003ECampaignCanManage\u003C/code\u003E\u0026nbsp;permission.\u0026nbsp;\u0026nbsp;\u003C/p\u003E\u003C/article\u003E\u003C/section\u003E\u003Csection class=\u0022faq\u0022\u003E\u003Ch3\u003EDoes the name of the role matter for permissions?\u003C/h3\u003E\u003Carticle\u003E\u003Cp\u003ENo, but we recommend using names such as \u0022Administrator\u0022 or \u0022Content Editors\u0022 to help indicate what the role is used for.\u003C/p\u003E\u003C/article\u003E\u003C/section\u003E\u003Csection class=\u0022faq\u0022\u003E\u003Ch3\u003EAre roles available for API calls?\u003C/h3\u003E\u003Carticle\u003E\u003Cp\u003ENo, all API calls have full permission to perform all actions in DailyStory available through the API.\u003C/p\u003E\u003C/article\u003E\u003C/section\u003E\u003Csection class=\u0022faq\u0022\u003E\u003Ch3\u003ECan I have two roles with the same name?\u003C/h3\u003E\u003Carticle\u003E\u003Cp\u003ENo, you are not allowed to have two roles with the same name.\u003C/p\u003E\u003C/article\u003E\u003C/section\u003E\u003Csection class=\u0022faq\u0022\u003E\u003Ch3\u003EA role\u0027s permission was changed, when will it apply to the users?\u003C/h3\u003E\u003Carticle\u003E\u003Cp\u003EPermissions are granted per session. Therefore, changes in a role\u0027s permissions are applied the next time the user logs in.\u003C/p\u003E\u003C/article\u003E\u003C/section\u003E\u003Csection class=\u0022faq\u0022\u003E\u003Ch3\u003EI changed permissions and locked myself out of the site.\u003C/h3\u003E\u003Carticle\u003E\u003Cp\u003EContact your site owner, they will need to log in and add your account to an appropriate role to grant you the permissions you need.\u003C/p\u003E\u003C/article\u003E\u003C/section\u003E\u003Cp\u003E\u003Cbr\u003E\u003C/p\u003E\r\n\u003Cscript type=\u0022application/ld\u002Bjson\u0022\u003E\r\n{\r\n  \u0022@context\u0022: \u0022https://schema.org\u0022,\r\n  \u0022@type\u0022: \u0022FAQPage\u0022,\r\n  \u0022mainEntity\u0022: [\r\n{\r\n    \u0022@type\u0022: \u0022Question\u0022,\r\n    \u0022name\u0022: \u0022A user is in two roles, which role grants their permissions?\u0022,\r\n    \u0022acceptedAnswer\u0022: {\r\n    \u0022@type\u0022: \u0022Answer\u0022,\r\n    \u0022text\u0022: \u0022DailyStory is designed to grant the highest level of permission given by the roles a user belongs to. If a user is in multiple roles and the first role does not grant a permission, e.g.\u0026nbsp; CampaignCanManage , but the second role does grant it, the user is given\u0026nbsp; CampaignCanManage \u0026nbsp;permission.\u0026nbsp;\u0026nbsp;\u0022\r\n    }\r\n},\r\n{\r\n    \u0022@type\u0022: \u0022Question\u0022,\r\n    \u0022name\u0022: \u0022Does the name of the role matter for permissions?\u0022,\r\n    \u0022acceptedAnswer\u0022: {\r\n    \u0022@type\u0022: \u0022Answer\u0022,\r\n    \u0022text\u0022: \u0022No, but we recommend using names such as \\\u0022Administrator\\\u0022 or \\\u0022Content Editors\\\u0022 to help indicate what the role is used for.\u0022\r\n    }\r\n},\r\n{\r\n    \u0022@type\u0022: \u0022Question\u0022,\r\n    \u0022name\u0022: \u0022Are roles available for API calls?\u0022,\r\n    \u0022acceptedAnswer\u0022: {\r\n    \u0022@type\u0022: \u0022Answer\u0022,\r\n    \u0022text\u0022: \u0022No, all API calls have full permission to perform all actions in DailyStory available through the API.\u0022\r\n    }\r\n},\r\n{\r\n    \u0022@type\u0022: \u0022Question\u0022,\r\n    \u0022name\u0022: \u0022Can I have two roles with the same name?\u0022,\r\n    \u0022acceptedAnswer\u0022: {\r\n    \u0022@type\u0022: \u0022Answer\u0022,\r\n    \u0022text\u0022: \u0022No, you are not allowed to have two roles with the same name.\u0022\r\n    }\r\n},\r\n{\r\n    \u0022@type\u0022: \u0022Question\u0022,\r\n    \u0022name\u0022: \u0022A role\u0027s permission was changed, when will it apply to the users?\u0022,\r\n    \u0022acceptedAnswer\u0022: {\r\n    \u0022@type\u0022: \u0022Answer\u0022,\r\n    \u0022text\u0022: \u0022Permissions are granted per session. Therefore, changes in a role\u0027s permissions are applied the next time the user logs in.\u0022\r\n    }\r\n},\r\n{\r\n    \u0022@type\u0022: \u0022Question\u0022,\r\n    \u0022name\u0022: \u0022I changed permissions and locked myself out of the site.\u0022,\r\n    \u0022acceptedAnswer\u0022: {\r\n    \u0022@type\u0022: \u0022Answer\u0022,\r\n    \u0022text\u0022: \u0022Contact your site owner, they will need to log in and add your account to an appropriate role to grant you the permissions you need.\u0022\r\n    }\r\n}\r\n    ]\r\n}\r\n\u003C/script\u003E",
      "publish_status": 0,
      "post_type": "Article",
      "featured_image_updating": false,
      "meta_description": "DailyStory supports a robust permissions model used to control what users can do on the platform. An administrator of the account can create different permissions with limited access to certain features. Important - enabling permissions has immediate impact to users. We recommend approaching permissions with a plan for who should and should not have access. Read before turning on permissions By default, permissions are \u0026#34;off\u0026#39;. With no permissions enabled, all users have full administr ...",
      "display_toc": true,
      "has_workingcopy": false,
      "allow_indexing": true,
      "total_views": 911,
      "date_published": "2024-08-17T09:32:35",
      "date_updated": "2026-03-17T19:34:14.893",
      "date_created": "2025-04-23T17:16:49.61"
    }
  }
}