What permissions are required to be able to edit the theme of the home Community group?

Hi Christopher G. Stanton 

I did some testing in my demo environment to confirm this, and unfortunately, there doesn't appear to be a way to grant theme/layout editing access to the root homepage without giving users full site administrator rights — at least not out of the box.

Initially, I explored an approach that seemed promising:

Attempted Approach (Did Not Work):

1. Create a site role specifically for your designers.

2. Navigate to the community homepage, hover over the pencil icon, and select Manage Group.

3. Go to Permissions, then the Site Roles tab.

4. Use "Show all roles" in the dropdown to select the custom role.

5. Scroll to the Group section and enable "Manage group theme."

Although this works for group-level themes, it does not grant access to edit the root homepage theme, which is tied to the overarching site configuration.

Partial Workaround:

A workaround that gets closer is this:

1. Create a custom site role for your designers.

2. Under the Permissions tab, enable “Manage site theme.”

This gives users in that role access to site-level theme and layout options, including the homepage. However, there are two caveats:

• They will also have access to edit other site pages (like profile pages, any custom pages, etc.).

• They can manage all themes, not just the homepage, so this may introduce broader access than desired.

What I would Recommend:

• Raising a feature request with Verint support for more granular theme-editing permissions — this is a common need for design teams that doesn’t always require full admin rights.

Sara Collins said:

Partial Workaround:

A workaround that gets closer is this:

1. Create a custom site role for your designers.

2. Under the Permissions tab, enable “Manage site theme.”

This gives users in that role access to site-level theme and layout options, including the homepage. However, there are two caveats:

• They will also have access to edit other site pages (like profile pages, any custom pages, etc.).

• They can manage all themes, not just the homepage, so this may introduce broader access than desired.

We currently do this, it's particularly the root homepage that we need to grant access to.

Sara Collins said:

Raising a feature request with Verint support for more granular theme-editing permissions — this is a common need for design teams that doesn’t always require full admin rights.

Is that different from the 'ideas' as a customer? Or creating a 'support case'? As I don't see a clear pathway to "feature request" with Verint? 

Yes - a feature request meaning an idea  in the customer community 

Sara Collins said:

Yes - a feature request meaning an idea  in the customer community

The turnaround time on those do not appear to be viable for issues that are affecting use of the site now, some of those ideas have been there for 3 to 4 years, this functionality appears rudimentary by comparison and necessity.

Sara Collins said:

Yes - a feature request meaning an idea  in the customer community

The turnaround time on those do not appear to be viable for issues that are affecting use of the site now, some of those ideas have been there for 3 to 4 years, this functionality appears rudimentary by comparison and necessity.