Skip to content

[People · Phase 1] Configure People role bindings in the production IdP #79

Closed

Description

@toto04

What

Production IdP configuration for Phase 1 (PoliNetworkOrg/admin#143), done once #78 is merged and deployed. Mostly configuration; one item needs a decision first.

Steps

  • Migrate: apply 0023_role_people_binding.

  • Binding permission: grant the new binding permission from [People · Phase 1] Let People manage bound roles, without preliminary people (rework of #73) #78 (e.g. idp:people:bind) to whoever should configure People. Master Admin has it implicitly; maybe it-lead.

  • Bind the roles. Team keys must match the backend's team list: it, hr, design, intl, events.

    Role Binding
    admin admin
    capo-admin capo
    hr-member / hr-lead team:hr:member / team:hr:lead
    design-member / design-lead team:design:member / team:design:lead
    intl-member / intl-lead team:intl:member / team:intl:lead
    events-member / events-lead team:events:member / team:events:lead
    IT team decide first, see below
  • IT team (decision needed). feat(people)!: let People manage bound roles through the backend #73's deploy notes bind it-core → team:it:member and it-lead → team:it:lead. That can't work: both grant idp:* permissions (idp:applications:write, idp:mcp, idp:roles:write, …), and roles carrying idp:* can't be bound.

    • Proposal: create plain team roles (e.g. it-member and it-team-lead, like the other teams' roles, with no permissions).
    • it-core and it-lead stay hand-assigned infrastructure-access roles.
  • people:self (decision needed). Should the bound roles grant it, so a linked person can open My area? Proposal: yes, on admin and every *-member role.

    • Leads and Capo Admins inherit it.
    • Board members already hold it, so bounded delegation keeps working.
  • people:link. Create the permission "People: Link accounts". It links a People record to a login account by hand, which gives that account the record's roles.

    • It implies people:read.
    • Grant it to direttivo.
    • It's deliberately separate from people:write, because linking hands roles to an account the system can't otherwise verify.
  • Backend client. Grant the internal scope idp:people:roles on its application page. Only Master Admin can change applications with API scopes. Reads work without it.

  • Check. Send one role command from the backend for a test account, and confirm the audit log shows via: people.

Done when

  • Every role above is bound, the backend client has idp:people:roles, people:link exists, and one end-to-end command has succeeded.

Activity

  1. added
    peoplePeople: Group Admins, Capo Admins, Teams, Soci and census (see the People roadmap)
    on Oct 29, 2026
  2. added theissue type on Oct 29, 2026
  3. coderabbitai commented on Oct 29, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #73 - feat(rbac): let People manage bound roles through the backend [open]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    peoplePeople: Group Admins, Capo Admins, Teams, Soci and census (see the People roadmap)

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions