{"id":46037,"date":"2018-08-30T10:13:51","date_gmt":"2018-08-30T10:13:51","guid":{"rendered":"https:\/\/www.sogolytics.com\/help\/?page_id=46037"},"modified":"2026-06-04T13:35:44","modified_gmt":"2026-06-04T13:35:44","slug":"users-permissions-workflows","status":"publish","type":"page","link":"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/","title":{"rendered":"Setting Sub-user Permissions"},"content":{"rendered":"<p>Permissions determine <strong>what a sub-user can access and do<\/strong> within the platform, including specific modules, features, and projects. By assigning the appropriate permissions and access rules, you can control each sub-user&#8217;s level of access, improve security, and ensure team members can only perform actions relevant to their role.<\/p>\n<div class=\"sogo-help-info-box\">\n<i class=\"fal fa-info-circle\"><\/i><\/p>\n<p class=\"sogo-info-text\">Permissions are only half of access control. They decide what a user can <strong>open<\/strong>; <strong>Data Visibility Rules<\/strong> decide what they can <strong>see inside<\/strong> what they open. See <a href=\"\/help\/data-visibility-rules-for-sub-users\/\" rel=\"noopener\">Data Visibility Rules for Sub-Users<\/a> for the second layer.<\/p>\n<\/div>\n<h2>Accessing Sub-user Permissions<\/h2>\n<ol>\n<li>To access <strong>User Management<\/strong>, click your <strong>Account Initials<\/strong> in the top-right corner and select <strong>Account Settings<\/strong> \u2192 <strong>User Management<\/strong>. Alternatively, click <strong>Account Settings<\/strong> at the bottom of the left-hand menu on the Home Page, then select <strong>User Management<\/strong>.<\/li>\n<li>On the User Management page, select the sub-user you want to configure.<\/li>\n<li>Click <strong>Set Permission<\/strong>. This opens the Set Permissions wizard.<\/li>\n<li>The wizard is organized into <strong>two tabs<\/strong> at the top, which together form the two layers of access control for a sub-user:\n<ul>\n<li><strong>Permissions<\/strong> \u2014 controls which projects, modules, and features the user can open.<\/li>\n<li><strong>Data Visibility<\/strong> \u2014 controls which records appear inside the items they&#8217;re allowed to open. See <a href=\"\/help\/data-visibility-rules-for-sub-users\/\" rel=\"noopener\">Data Visibility Rules for Sub-Users<\/a>.<\/li>\n<\/ul>\n<li>Across the top of the <strong>Permissions<\/strong> tab, you&#8217;ll see a row of sub-tabs \u2014 one for each area you can configure: <strong>Projects<\/strong>, <strong>Directories<\/strong>, <strong>Contact Lists<\/strong>, <strong>Email Templates<\/strong>, <strong>Custom Dashboards<\/strong>, <strong>CX Dashboard<\/strong>, <strong>EX Dashboard<\/strong>, <strong>Saved Reports<\/strong>, <strong>Salesforce<\/strong>, <strong>File Library<\/strong>, <strong>Project Calendar<\/strong>, and <strong>Custom Text and Labels<\/strong>.<\/li>\n<li>Select the area you want to configure, set the access options, and click <strong>Save<\/strong> or <strong>Save &amp; Go Back<\/strong>. The updated permissions apply to the selected sub-user.<\/li>\n<\/ol>\n<p class=\"sogo-help-sub-head\">Navigate to<\/p>\r\n<ul class=\"sogo-help-sub-list\">\r\n    <li><a href=\"#section-1\">Permissions for Project<\/a><\/li>\r\n    <li><a href=\"#section-2\">Permissions for Directory<\/a><\/li>\r\n<li><a href=\"#section-3\">Permissions for Contact Lists<\/a><\/li>\r\n<li><a href=\"#section-4\">Permissions for Email templates <\/a><\/li>\r\n<li><a href=\"#section-5\">Permissions for Custom Dashboards<\/a><\/li>\r\n<li><a href=\"#section-6\">Permissions for Saved Reports<\/a><\/li>\r\n<li><a href=\"#section-7\">Permissions for Salesforce<\/a><\/li>\r\n<li><a href=\"#section-8\">Permissions for File Library<\/a><\/li>\r\n<li><a href=\"#section-9\">Permissions for Project Calendar<\/a><\/li>\r\n<\/ul>\n<h3 id=\"section-1\">Permissions for Projects<\/h3>\n<p>\nProject permissions determine a sub-user&#8217;s access to the <strong>Design<\/strong>, <strong>Distribution<\/strong>, <strong>Report<\/strong>, and <strong>Data<\/strong> modules within a project. These permissions are divided into two sections:\n<\/p>\n<ul>\n<li><strong>Future Projects<\/strong> \u2013 Defines the access that will be assigned automatically to projects created in the future.<\/li>\n<li><strong>Existing Projects<\/strong> \u2013 Defines access for projects that already exist in the account.<\/li>\n<\/ul>\n<h3>Permissions for Future Projects<\/h3>\n<p>\nThese permissions are applied automatically whenever a new project is created.\n<\/p>\n<ul>\n<li>\n        <strong>For all future projects this user creates<\/strong> \u2013 Controls which modules the user can access in projects they create themselves.\n    <\/li>\n<li>\n        <strong>For all future projects created by other users<\/strong> \u2013 Controls which modules the user can access in projects created by other users in the account.\n    <\/li>\n<\/ul>\n<h3>Permissions for Existing Projects<\/h3>\n<p>\nUse this section to manage access to projects that already exist in the account.\n<\/p>\n<ol>\n<li>\n        Select a folder using the <strong>Folder<\/strong> dropdown, or enable <strong>All Folders<\/strong> to display projects from every folder.\n    <\/li>\n<li>\n        Use the <strong>Search<\/strong> box to locate a specific project by name.\n    <\/li>\n<li>\n        For each project, select the modules the user should be able to access, including <strong>Design<\/strong>, <strong>Distribution<\/strong>, <strong>Report<\/strong>, and <strong>Data<\/strong>.\n    <\/li>\n<li>\n        To apply the same permission to all displayed projects, use the checkbox in the corresponding column header.\n    <\/li>\n<\/ol>\n<p>\nOnce you have finished configuring permissions, click <strong>Save<\/strong> or <strong>Save &amp; Go Back<\/strong>.\n<\/p>\n<p><img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS1.png\"\/><\/p>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nA field researcher should build and send surveys but never see raw data. Under <strong>Permissions for Future Projects<\/strong>, you check <strong>Design<\/strong> and <strong>Distribute<\/strong> but leave <strong>Report<\/strong> and <strong>Data<\/strong> unchecked \u2014 so every new survey they create is theirs to design and distribute, with results hidden.<br \/>\n<\/span>\n  <\/div>\n<h3>Set Workflow for Distribution<\/h3>\n<p>\nIf a sub-user has access to the <strong>Distribution<\/strong> module, the account administrator can enable <strong>Set Workflow<\/strong>. When enabled, the sub-user must obtain approval from a designated <strong>Workflow Manager<\/strong> before distributing a survey. The Workflow Manager receives an email request, and the survey is distributed only after approval is granted.\n<\/p>\n<p>\nTo learn more about Workflow Management, <a href=\"\/help\/workflow-management\/\" rel=\"noopener\">click here<\/a>.\n<\/p>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nNew hires shouldn&#8217;t email customers without a review. You enable Workflow for Distribution on their account, so every send pauses for a manager&#8217;s approval first.<br \/>\n<\/span>\n  <\/div>\n<h2 id=\"section-2\">Permissions for Directory<\/h2>\n<p><strong>Set Permissions for Directories<\/strong> \u2014 determines which directories a user can access and edit and defines the level of contact data they can view within those directories. By default, users have full access to any directories they create. This wizard allows administrators to grant access to directories created by other users.<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Allow user to Create Directories<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>When enabled, the user can create and manage their own directories.\n<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>READ\/USE access to all future Directories<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>When enabled it auto-grants View and Use access to every directory created by other users<\/td>\n<\/tr>\n<tr class=\"column-bg-white-effect\">\n<td>View Sensitive Data in All Future Directories<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>\nControls whether the user can view sensitive data fields in all future directories created by other users. When disabled, these fields remain masked.\n<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>EDIT access to all future Directories<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Lets the user modify all future directories created by others.<\/td>\n<\/tr>\n<tr class=\"column-bg-white-effect\">\n<td>Permissions for All Existing Directories<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>\nUse this section to manage a sub-user&#8217;s access to existing directories. Each directory appears as a separate row in the table and provides three independent permissions: <strong>Permission to Use<\/strong>, <strong>View Sensitive Data<\/strong>, and <strong>Permission to Edit<\/strong>. Enable the required permissions for each directory based on the level of access you want the sub-user to have.\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"sogo-help-info-box\">\n<i class=\"fal fa-info-circle\"><\/i><\/p>\n<p class=\"sogo-info-text\"><strong>View Sensitive Data<\/strong> is a <strong>separate<\/strong> permission from Use and Edit \u2014 this is what lets you give someone working access to a directory while still hiding personal data.\n<\/p>\n<\/div>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nA campaign coordinator needs to send to the <strong>Customer Directory<\/strong> but must not see personal contact details. You tick <strong>Permission to Use<\/strong> on that row and leave <strong>View Sensitive Data<\/strong> unchecked \u2014 they can build distributions against the directory, but email and phone columns stay masked.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS2.png\" \/><\/p>\n<h2>Permissions for Contact Lists<\/h2>\n<p><strong>Set Permissions for Contact Lists<\/strong> \u2014 controls which contact lists the user can use and edit. By default, users have full access to lists they create; this wizard assigns additional access to lists created by others.<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>READ\/USE access to all future Contact Lists<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Auto-grants view\/use access to every list other users create going forward.<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>EDIT access to all future Contact Lists<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Lets the user edit all future lists created by others (read\/use included automatically).<\/td>\n<\/tr>\n<tr class=\"column-bg-white-effect\">\n<td>Permissions for all existing Contact Lists<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>A searchable table of current lists, each with Permission to Use and Permission to Edit checkboxes. Header checkboxes apply a column to every visible list.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nA contact-list manager needs to maintain shared lists. You turn on <strong>EDIT access to all future Contact Lists<\/strong> \u2014 which also grants Read\/Use \u2014 so they can clean and update any list the team creates, now or later.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS3.png\" \/><\/p>\n<h2>Permissions for Email Templates<\/h2>\n<p><strong>Set Permissions for Email Templates<\/strong> \u2014 controls access to email templates and which sender domains the user may use.<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Allow access to all Email Templates<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>When on, the user has full access to all system-defined email templates as well as custom ones created by other users. Turn it off to assign granular permissions.<\/td>\n<\/tr>\n<tr class=\"column-bg-white-effect\">\n<td>Use access to all future Email Templates.<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>When on, allows the sub-user to see and use all future Email Templates uploaded by other users.\n<\/td>\n<\/tr>\n<tr class=\"column-bg-white-effect\">\n<td>Permission for existing Email Templates.<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>\nWhen enabled, existing email templates become available for permission assignment. Select the <em>Permission to Use<\/em> checkbox for any template that the sub-user should be allowed to access and use.\n<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>Sender Domain Restriction<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>When on, sets restrictions on the domains that can be used as sender email addresses for this user. Use it to ensure a user can only send from approved, authenticated domains.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nYou want new hires to send only from your verified <strong>@company.com<\/strong> domain. You enable <strong>Sender Domain Restriction<\/strong> and limit them to that domain, so they can&#8217;t accidentally send from an unverified address.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS4.png\"  \/><\/p>\n<h2>Permissions for  Custom Dashboards<\/h2>\n<p><strong>Set Permissions for Custom Dashboards<\/strong> \u2014 controls who can build dashboards and which existing ones the user can open or edit. By default, users have full access to all custom dashboards they create.<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Allow user to Create Dashboards<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>When on, the user can build their own custom dashboards. Turn off for view-only consumers.<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>READ\/USE access to all future Custom Dashboard<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Auto-grants view\/use access to every dashboard other users create later.<\/td>\n<\/tr>\n<tr class=\"column-bg-white-effect\">\n<td>EDIT access to all future Custom Dashboard<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Lets the user edit all future dashboards created by others (read\/use included).<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>Permissions for all existing Custom Dashboards<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>A searchable table of current dashboards with Permission to Use and Permission to Edit checkboxes per row, plus header checkboxes to set a column for all.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Remember this tab governs <strong>Custom Dashboards<\/strong> only. <strong>CX Dashboard<\/strong> and <strong>EX Dashboard<\/strong> are separate tabs with their own tab-level rules \u2014 see <a href=\"\/help\/managing-cx-ex-dashboard-access\/\" rel=\"noopener\">Managing CX\/EX Dashboard Access<\/a>.<\/p>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nAn executive should read the team&#8217;s dashboards but never change them. You turn <strong>Allow user to Create Dashboards<\/strong> off, turn <strong>READ\/USE access to all future Custom Dashboard<\/strong> on, and leave Edit off \u2014 they always see the latest dashboards, view-only.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS5.png\" \/><\/p>\n<h2>Permissions for Saved Reports<\/h2>\n<p><strong>Set Permission for Saved Reports<\/strong> \u2014 controls which saved reports the user can open. By default, users have full access to all saved reports they create.<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Access for all future saved reports<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Allow automatic access to all future saved reports created by other users. When on, every report anyone else saves from now on is automatically available \u2014 no need to return to this wizard.<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>Access for all existing saved reports<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>A searchable, paginated table of reports that already exist. Each row shows Report Name, Project Name, Tool, Folder, and Report Type, with a single Allow Access checkbox to grant that report. Use the header Allow Access checkbox to grant every report on the page at once.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Unlike Contact Lists or Directories, Saved Reports has a <strong>single Allow Access<\/strong> checkbox per report (there&#8217;s no separate edit level) \u2014 access here means the user can open and view the saved report.<\/p>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nA stakeholder needs to follow two specific reports but nothing else. You leave <strong>Access for all future saved reports<\/strong> off, search the existing list for each report by name, and tick <strong>Allow Access<\/strong> only on those two rows.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS8.png\" \/><\/p>\n<h2>Permissions for Salesforce<\/h2>\n<p><strong>Set Permissions for Salesforce<\/strong> \u2014 controls how the user can interact with your connected Salesforce integration. Each capability is an independent toggle, named after the user.<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Allow [user] to push data into Salesforce<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Lets the user send Sogolytics data out to Salesforce.<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>Allow [user] to import\/read data from Salesforce<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Lets the user pull Salesforce records into Sogolytics (for example, to build a directory or distribute a survey).<\/td>\n<\/tr>\n<tr class=\"column-bg-white-effect\">\n<td>Allow [user] to see Salesforce activity log<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Lets the user view the log of Salesforce sync activity.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Because each direction is separate, you can grant read-only integration access without allowing the user to push anything back.<\/p>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nAn analyst should be able to bring Salesforce contacts into Sogolytics but must never write data back. You turn on <strong>import\/read data from Salesforce<\/strong> and leave <strong>push data into Salesforce<\/strong> off.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS9.png\" \/><\/p>\n<h2>Permissions for File Library<\/h2>\n<p><strong>Set Permission for File Library<\/strong> \u2014 controls which shared files the user can see and use. By default, users have full access to all files they upload.<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Use Access to all future Files<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Allow this user to see and use all future files uploaded by other users. When on, every file uploaded later is automatically available.<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>Permissions for all existing Files<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>A searchable table of files already in the library, each with a single Permission to Use checkbox. The header checkbox grants every listed file at once.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>The File Library uses a single <strong>Permission to Use<\/strong> level \u2014 there&#8217;s no separate edit permission, because library files are shared assets to be used rather than altered.<\/p>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nA designer needs the shared logo and banner files for survey themes. You search the existing files and tick <strong>Permission to Use<\/strong> on those assets, leaving the rest unticked.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS10.png\" \/><\/p>\n<h2>Permissions for Project Calendar<\/h2>\n<p><strong>Set Permissions for Project Calendar<\/strong> \u2014 controls whether the user can see and change the shared project calendar. Two simple toggles:<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Allow user to view Project Calendar<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Turn on so the user can see scheduled project activity.<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>Allow user to modify Project Calendar<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Turn on to let the user add or change calendar entries. Pair it with view access.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nA coordinator should keep the calendar current, so you turn on both <strong>view<\/strong> and <strong>modify<\/strong>. A read-only stakeholder gets <strong>view<\/strong> on, <strong>modify<\/strong> off \u2014 they can see the schedule but can&#8217;t change it.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS11.png\"  \/><\/p>\n<h2>Permissions for Custom Text and Labels<\/h2>\n<p><strong>Set Permissions for Custom Text and Labels<\/strong> \u2014 controls whether the user can see and change your account&#8217;s custom wording and labels. Two toggles:<\/p>\n<div class=\"package-table-container no-scroll\">\n<table class=\"package-limit-table\" border=\"0\" cellpadding=\"0\">\n<thead>\n<tr>\n<td>Control<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>What it does<\/td>\n<\/tr>\n<\/thead>\n<tbody>\n<tr class=\"column-bg-white-effect\">\n<td>Allow user to view Custom Text and Labels<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Allow this user to view the Custom Text and Labels.<\/td>\n<\/tr>\n<tr class=\"column-bg-effect\">\n<td>Allow user to modify Custom Text and Labels<\/td>\n<td class=\"min-spacer\"><\/td>\n<td>Allow this user to modify the Custom Text and Labels.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<div class=\"sogo-help-info-box\">\n<i class=\"fal fa-info-circle\"><\/i><\/p>\n<p class=\"sogo-info-text\"><strong>Important:<\/strong> Custom Text and Labels are <strong>account-wide<\/strong>. Any change a user makes here affects your <strong>entire organizational account<\/strong>, not just their own projects \u2014 so grant <strong>modify<\/strong> access sparingly, and reserve it for trusted administrators.<\/p>\n<\/div>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nYou want a brand manager to refine product terminology everywhere, so you grant both <strong>view<\/strong> and <strong>modify<\/strong>. For everyone else you leave <strong>modify<\/strong> off to protect the account-wide wording.<br \/>\n<\/span>\n  <\/div><br \/>\n<img decoding=\"async\" src=\"\/help\/wp-content\/uploads\/2026\/06\/UMPS12.png\" \/><\/p>\n<div class=\"sogo-help-info-box\">\n<i class=\"fal fa-info-circle\"><\/i><\/p>\n<p class=\"sogo-info-text\"><strong>Tip:<\/strong> If more tabs exist than fit on wizard, use the <strong>\u2039 \u203a<\/strong> arrows at the right end of the tab strip to scroll to <strong>File Library<\/strong>, <strong>Project Calendar<\/strong>, and <strong>Custom Text and Labels<\/strong>.<\/p>\n<\/div>\n<h2 id=\"section-4\">Copy another user&#8217;s permissions<\/h2>\n<p>Rather than rebuilding a setup from scratch, you can copy one already in place.<\/p>\n<p>On the permissions wizard, use <strong>Copy Another User&#8217;s Permissions<\/strong> (also available as <strong>Duplicate Permission<\/strong> at the top of the Projects view). Choose the user to copy from and which permissions to bring over.<\/p>\n<div class=\"example-block-container blue-shade\">\n        <span class=\"example-block-content\"><span class=\"example-block-header\">For example:<\/span><br \/>\nYou&#8217;ve fully configured <strong>analyst_01<\/strong>. When <strong>analyst_02<\/strong> joins the same team, open their permissions, choose <strong>Copy Another User&#8217;s Permissions<\/strong>, pick <strong>analyst_01<\/strong>, and their access is mirrored in seconds \u2014 then tweak any differences.<br \/>\n<\/span>\n  <\/div>\n<h2 id=\"section-5\">Saving and reviewing<\/h2>\n<ul>\n<li>Most areas offer <strong>Save<\/strong> and <strong>Save &amp; Go Back<\/strong>.<\/li>\n<li>To audit everything you&#8217;ve assigned, return to User Management and use the export option to download all sub-user permissions to Excel.<\/li>\n<\/ul>\n<h2 id=\"section-6\">Related articles<\/h2>\n<ul>\n<li><a href=\"\/help\/managing-cx-ex-dashboard-access\/\" rel=\"noopener\">Managing CX\/EX Dashboard Access<\/a><\/li>\n<li><a href=\"\/help\/data-visibility-rules-for-sub-users\/\" rel=\"noopener\">Data Visibility Rules for Sub-Users<\/a><\/li>\n<li><a href=\"\/help\/introduction-manage-sub-users\/\" rel=\"noopener\">Introduction to Managing Sub-Users<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the appropriate permissions and access rules, you can control each sub-user&#8217;s level of access, improve security, and ensure team members can only perform actions relevant to their role. Permissions are only half of access control. They decide what a user can open; Data Visibility Rules decide what they can see inside what they open. See Data Visibility Rules for Sub-Users for the second layer. Accessing Sub-user Permissions To access User Management, click your Account Initials in the top-right corner and select Account Settings \u2192 User Management. Alternatively, click Account Settings at the bottom of the left-hand menu on the Home Page, then select User Management. On the User Management page, select the sub-user you want to configure. Click Set Permission. This opens the Set Permissions wizard. The wizard is organized into two tabs at the top, which together form the two layers of access control for a sub-user: Permissions \u2014 controls which projects, modules, and features the user can open. Data Visibility \u2014 controls which records appear inside the items they&#8217;re allowed to open. See Data Visibility Rules for Sub-Users. Across the top of the Permissions tab, you&#8217;ll see a row of sub-tabs \u2014 one for each area you can configure: Projects, Directories, Contact Lists, Email Templates, Custom Dashboards, CX Dashboard, EX Dashboard, Saved Reports, Salesforce, File Library, Project Calendar, and Custom Text and Labels. Select the area you want [&hellip;]<\/p>\n","protected":false},"author":26,"featured_media":0,"parent":0,"menu_order":298,"comment_status":"closed","ping_status":"closed","template":"sogo_new_design.php","meta":{"footnotes":""},"categories":[203],"tags":[497,498,499,489,491,286],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v19.7.2 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Setting Sub-user Permissions - Sogolytics<\/title>\n<meta name=\"description\" content=\"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Setting Sub-user Permissions - Sogolytics\" \/>\n<meta property=\"og:description\" content=\"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/\" \/>\n<meta property=\"og:site_name\" content=\"Sogolytics\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-04T13:35:44+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/\",\"url\":\"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/\",\"name\":\"Setting Sub-user Permissions - Sogolytics\",\"isPartOf\":{\"@id\":\"https:\/\/www.sogolytics.com\/help\/#website\"},\"datePublished\":\"2018-08-30T10:13:51+00:00\",\"dateModified\":\"2026-06-04T13:35:44+00:00\",\"description\":\"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the\",\"breadcrumb\":{\"@id\":\"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.sogolytics.com\/help\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Setting Sub-user Permissions\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.sogolytics.com\/help\/#website\",\"url\":\"https:\/\/www.sogolytics.com\/help\/\",\"name\":\"Sogolytics\",\"description\":\"Sogolytics - Online Survey Tool\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.sogolytics.com\/help\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Setting Sub-user Permissions - Sogolytics","description":"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/","og_locale":"en_US","og_type":"article","og_title":"Setting Sub-user Permissions - Sogolytics","og_description":"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the","og_url":"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/","og_site_name":"Sogolytics","article_modified_time":"2026-06-04T13:35:44+00:00","twitter_card":"summary","twitter_misc":{"Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/","url":"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/","name":"Setting Sub-user Permissions - Sogolytics","isPartOf":{"@id":"https:\/\/www.sogolytics.com\/help\/#website"},"datePublished":"2018-08-30T10:13:51+00:00","dateModified":"2026-06-04T13:35:44+00:00","description":"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the","breadcrumb":{"@id":"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.sogolytics.com\/help\/users-permissions-workflows\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.sogolytics.com\/help\/"},{"@type":"ListItem","position":2,"name":"Setting Sub-user Permissions"}]},{"@type":"WebSite","@id":"https:\/\/www.sogolytics.com\/help\/#website","url":"https:\/\/www.sogolytics.com\/help\/","name":"Sogolytics","description":"Sogolytics - Online Survey Tool","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.sogolytics.com\/help\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"}]}},"seo_meta_info":{"yoast_noindex":"","rankmath_noindex":"","yoast_title":"Setting Sub-user Permissions","yoast_desc":"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the appropriate permissions and access&hellip;","rankmath_title":"Setting Sub-user Permissions","rankmath_desc":"Permissions determine what a sub-user can access and do within the platform, including specific modules, features, and projects. By assigning the appropriate permissions and access&hellip;"},"_links":{"self":[{"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/pages\/46037"}],"collection":[{"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/comments?post=46037"}],"version-history":[{"count":51,"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/pages\/46037\/revisions"}],"predecessor-version":[{"id":60214,"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/pages\/46037\/revisions\/60214"}],"wp:attachment":[{"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/media?parent=46037"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/categories?post=46037"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sogolytics.com\/help\/wp-json\/wp\/v2\/tags?post=46037"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}