MANSOQ Knowledge
← Knowledge library

Facility administration

Maintain department metadata and distinguish browsing from administration

Compare actual Doctor browsing with authorized department editing, recognize disabled name/unchanged states, save notes and verify existing Staff/Doctor memberships separately.

Current source · Actual synthetic Doctor read-only directory and separate local-superuser notes-only department update in the same Clinic. Normal department GET200 verifies persistence and normal membership GET200 confirms original Staff/Doctor assignments. No negative department write, role expansion, deletion, reparenting, inactive transition or all-role/facility audit is claimed. · 7 min read

Before you begin

1. Recognize department browsing without maintenance authority

The synthetic Doctor can read its accessible SYNTHETIC Outpatient Department row in this Clinic, but the pictured view has no Add or pencil maintenance controls. A normal same-Doctor department list read returned200. Browsing a department is distinct from permission to create or manage one; no department write was attempted under this Doctor session.

Recognize department browsing without maintenance controls. Actual full desktop MANSOQ with synthetic Clinic configuration.12
Recognize department browsing without maintenance controls · 2026-10-18Actual1920×1080 Chrome pixels, source f6e9f05f. Separate Doctor read-only and local superuser metadata-maintenance sessions, same synthetic Clinic. No role, membership, deletion or clinical operation.
  1. Accessible department: Viewing this row does not grant department maintenance.
  2. Maintenance controls absent: The Doctor view has no Add or edit controls in this captured context.

2. Use the intended operational row in an authorized session

In the separate authorized local training administrator session, the same Clinic directory includes the operational department’s pencil control and the reserved Administration root row. Confirm SYNTHETIC Outpatient Department and use its pencil to open Edit Department/Team. Do not substitute the root row or a user-membership Edit action.

Choose the operational department’s maintenance control. Actual full desktop MANSOQ with synthetic Clinic configuration.123
Choose the operational department’s maintenance control · 2026-10-18Actual1920×1080 Chrome pixels, source f6e9f05f. Separate Doctor read-only and local superuser metadata-maintenance sessions, same synthetic Clinic. No role, membership, deletion or clinical operation.
  1. Intended operational department: Confirm the exact existing department before editing.
  2. Edit this department: This row action is separate from membership-role editing.
  3. Reserved Administration root: This root row is distinct from the operational department.

3. Read editable fields and the unchanged state

The edit sheet loads Name, Type and Description. Update Organization is disabled before an actual valid change. Department/Team type is a configuration classification, separate from a person’s security role. No active/inactive or parent-choice control is exposed in this actual form.

Read existing department fields and unchanged Update state. Actual full desktop MANSOQ with synthetic Clinic configuration.123
Read existing department fields and unchanged Update state · 2026-10-18Actual1920×1080 Chrome pixels, source f6e9f05f. Separate Doctor read-only and local superuser metadata-maintenance sessions, same synthetic Clinic. No role, membership, deletion or clinical operation.
  1. Existing department identity: Preserve the intended identity during a notes-only change.
  2. Department or Team type: This is separate from a user security role.
  3. Unchanged update disabled: Change a valid editable field before normal update.

4. Restore a required name before updating

When the required Name is empty, Update Organization remains disabled. Restore the correct department name before proceeding. This image qualifies a disabled invalid-form state; it does not represent a server rejection or an invalid saved record.

Restore a required department name before the update is enabled. Actual full desktop MANSOQ with synthetic Clinic configuration.12
Restore a required department name before the update is enabled · 2026-10-18Actual1920×1080 Chrome pixels, source f6e9f05f. Separate Doctor read-only and local superuser metadata-maintenance sessions, same synthetic Clinic. No role, membership, deletion or clinical operation.
  1. Required name empty: Restore the approved department name before retrying.
  2. Invalid update disabled: The button remains disabled while required Name is empty.

5. Review the notes-only change and update

This example restores the original name, retains Department type and changes Description to clearly synthetic review notes. Check the intended record and select the enabled Update Organization button. No user role, membership, hierarchy or active-state change is part of this operation.

Review restored identity, Department type and changed notes before Update Organization. Actual full desktop MANSOQ with synthetic Clinic configuration.123
Review restored identity, Department type and changed notes before Update Organization · 2026-10-18Actual1920×1080 Chrome pixels, source f6e9f05f. Separate Doctor read-only and local superuser metadata-maintenance sessions, same synthetic Clinic. No role, membership, deletion or clinical operation.
  1. Original name restored: The same department remains selected.
  2. Notes-only change: This does not assign users or qualify clinical workflows.
  3. Update Organization: Save the reviewed valid department metadata.

6. Verify saved department detail

Open the saved department row and read the original heading, Department badge and updated description. A separate normal detail GET returned200 and confirmed the same identity, type, active state and original absent-parent reference. The Users tab is separate from these department metadata fields.

Verify the saved department notes and separate the membership tab. Actual full desktop MANSOQ with synthetic Clinic configuration.123
Verify the saved department notes and separate the membership tab · 2026-10-18Actual1920×1080 Chrome pixels, source f6e9f05f. Separate Doctor read-only and local superuser metadata-maintenance sessions, same synthetic Clinic. No role, membership, deletion or clinical operation.
  1. Saved existing department: Confirm exact department identity after the sheet closes.
  2. Saved updated notes: Read persisted detail, not just a success toast.
  3. Membership remains separate: User-role maintenance is a different task from department notes.

7. Inspect existing members separately

In Users, the original synthetic Staff and Doctor cards retain their roles. A normal membership GET returned200 and matched their original membership IDs and role names. Add User, Link User and the card’s Edit action are separate identity/membership operations; none was submitted during this department metadata update.

Inspect retained Staff and Doctor memberships after department notes maintenance. Actual full desktop MANSOQ with synthetic Clinic configuration.1234
Inspect retained Staff and Doctor memberships after department notes maintenance · 2026-10-18Actual1920×1080 Chrome pixels, source f6e9f05f. Separate Doctor read-only and local superuser metadata-maintenance sessions, same synthetic Clinic. No role, membership, deletion or clinical operation.
  1. Department Users view: Confirm the department before interpreting membership cards.
  2. Existing Staff role: This is the saved membership role, not a display suffix.
  3. Existing Doctor role: The prior practitioner membership remains unchanged.
  4. Link existing identity separately: Department notes updates do not assign users.

What the current form supports

The pinned schema contains name, description and Department/Team type. Its submission carries parent context supplied by the caller; it does not offer a parent picker or active/inactive toggle. Do not invent reparenting or deactivate/reactivate steps from model fields that the current UI does not expose.

Different controls use different rights

The directory displays Add for create rights and pencil maintenance for manage rights (or geographic administrator context), while the reserved root row excludes the ordinary edit/delete controls. Backend department-object management checks the target department ancestry, facility root and geographic scope. Role names or sidebar visibility alone do not establish an effective authorization result.

Membership maintenance has an additional boundary

Linking or changing an organizational user role is separate from editing department notes. The pinned backend checks both membership-management permission and, outside superuser/geographic-admin handling, that the requested role permissions are within the administrator’s existing role envelope. This guide does not assign a different role or certify every delegation boundary.

Troubleshooting

I can read departments but cannot see maintenance controls

Confirm the intended operation and authorized account with the deployment administrator. The captured Doctor browsing view intentionally has no maintenance controls; do not broaden a role merely because a menu is visible.

Update Organization is disabled

Check that a required valid name is present and an editable value has actually changed. The source also disables Update during a pending request.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.