uuid:
  - value: 0656f37b-0273-45c3-9421-b7d2a59180e3
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-07-30T22:22:41+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: "Don't share user accounts"
created:
  - value: '2025-07-26T21:35:11+00:00'
changed:
  - value: '2025-07-30T22:22:41+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: ''
    pid: null
    langcode: en
body:
  - value: |-
      Another common Drupal issue I see is shared user accounts that are used by more than one person.

      These commonly have generic names like "Administrator" or "Editor" instead of the name of an individual.

      But, with Drupal's flexible user system, why would you need to do this?

      If you have a shared account, you don't know who made a change when looking at a list of revisions and you can't easily block or delete an account when someone leaves the team without affecting everyone else.

      With no need for any additional modules or services, you can create as many user accounts as you need, with functionality for registering new accounts, logging in and resetting passwords available by default.

      Any user can have multiple roles - each with specific permissions to allow the user to perform specific tasks.

      You can make the roles as fine-grained as you need - with a role only having one additional permission, if that's what is needed.

      Have an individual user account for each person who needs one, and as many roles as you need to give each person exactly the permissions they need.
    format: markdown
    processed: |
      <p>Another common Drupal issue I see is shared user accounts that are used by more than one person.</p>
      <p>These commonly have generic names like "Administrator" or "Editor" instead of the name of an individual.</p>
      <p>But, with Drupal's flexible user system, why would you need to do this?</p>
      <p>If you have a shared account, you don't know who made a change when looking at a list of revisions and you can't easily block or delete an account when someone leaves the team without affecting everyone else.</p>
      <p>With no need for any additional modules or services, you can create as many user accounts as you need, with functionality for registering new accounts, logging in and resetting passwords available by default.</p>
      <p>Any user can have multiple roles - each with specific permissions to allow the user to perform specific tasks.</p>
      <p>You can make the roles as fine-grained as you need - with a role only having one additional permission, if that's what is needed.</p>
      <p>Have an individual user account for each person who needs one, and as many roles as you need to give each person exactly the permissions they need.</p>
    summary: ''
field_daily_email_cta:
  - target_type: node
    target_uuid: 9b4c39a3-702f-486c-a79b-4d7b96a4f3f6