64 lines
2.9 KiB
YAML
64 lines
2.9 KiB
YAML
uuid:
|
|
- value: 4f9589eb-52d9-4c65-bf7d-48990e359631
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-07-28T23:23:20+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: "It's hard to take things away"
|
|
created:
|
|
- value: '2025-07-23T23:21:58+00:00'
|
|
changed:
|
|
- value: '2025-07-28T23:23:20+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2025/07/23/its-hard-take-things-away
|
|
langcode: en
|
|
body:
|
|
- value: |-
|
|
A common issue I see on Drupal projects is how the user roles and permissions have been configured.
|
|
|
|
They are usually set up correctly to begin with, with users given the correct roles with only the permissions they need to perform their required tasks.
|
|
|
|
But, at some point, something doesn't work or a user needs access to something new.
|
|
|
|
Rather than assign them a new role, the user is commonly given a role that gives them access to too much - usually an Administrator role that lets them access anything in the Drupal admin UI.
|
|
|
|
As well as introducing security risks, when a user has access to all the settings, they will use them and it is very difficult to review and change user roles and permissions once they have been assigned without causing disruption.
|
|
|
|
It may be tempting, particularly if there is pressure or deadlines, but avoid giving roles and permissions they don't need.
|
|
|
|
Once they are given, they are hard to take away.
|
|
format: markdown
|
|
processed: |
|
|
<p>A common issue I see on Drupal projects is how the user roles and permissions have been configured.</p>
|
|
<p>They are usually set up correctly to begin with, with users given the correct roles with only the permissions they need to perform their required tasks.</p>
|
|
<p>But, at some point, something doesn't work or a user needs access to something new.</p>
|
|
<p>Rather than assign them a new role, the user is commonly given a role that gives them access to too much - usually an Administrator role that lets them access anything in the Drupal admin UI.</p>
|
|
<p>As well as introducing security risks, when a user has access to all the settings, they will use them and it is very difficult to review and change user roles and permissions once they have been assigned without causing disruption.</p>
|
|
<p>It may be tempting, particularly if there is pressure or deadlines, but avoid giving roles and permissions they don't need.</p>
|
|
<p>Once they are given, they are hard to take away.</p>
|
|
summary: ''
|
|
field_daily_email_cta:
|
|
- target_type: node
|
|
target_uuid: e3f6c728-7855-4804-8614-e2a0c08c368f
|