Permission granularity for domain-specific administration

Created on 7 December 2009, about 15 years ago

Updated 3 September 2024, 5 months ago

It appears that an editor assigned to a domain requires the 'administer domains' permission in order to alter any domain-specific theme settings. But this then grants access to all domain settings, not just to the assigned domain(s).

The use case I'm trying to achieve would allow an editor to choose and configure a theme for his/her assigned domain, without granting access to default or other domain settings. Ideally, a subset of all active themes could be presented to such domain editors, so that the default domain's theme, along with administrative themes could be excluded.

✨ Feature request

Status

Closed: outdated

Version

3.0

Component

Code

Created by

🇨🇦Canada ergonlogic Montréal, Québec 🇨🇦

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 5 months ago →
🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
I'll close this issue due to inactivity for 12 years and upcoming EOL of Drupal 7 in January 2025 → . While the project's version for Drupal 7 will surely keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. A big thanks around for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024