starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 00:06:06 +03:00

[GH-ISSUE #5404] [Feature Request]: Visually Distinguish Global vs Tenant‑Scoped Menu Items #2603

New issue

Open

opened 2026-03-02 13:53:41 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:53:41 +03:00

Owner

Originally created by @Lowell-Syncrety on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5404

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

CIPP currently mixes global and tenant‑scoped functionality within the same navigation sections, which is logical from a workflow perspective but not visually obvious to the operator.

For example, under Identity Management → Administration, tenant‑specific items like Users and Groups appear alongside Group Templates, which are global in scope. While the placement makes sense functionally, there is no visual indication that actions taken in Group Templates affect all tenants rather than the currently selected tenant.

This creates confusion, particularly for:

New technicians
Junior staff
Anyone working quickly under the assumption that the selected tenant context applies to all nearby actions

The risk is not theoretical: modifying a global object while believing you are operating tenant‑locally can result in unintended cross‑tenant impact. As an admin myself I'm still running into this and have to double-check other clues in the resulting UX page to make sure I'm doing something global or tenant-specific.

Benefits for MSPs

Reduced operational risk: Clear scope indicators help prevent accidental global changes when a technician believes they are working within a single tenant.
Faster onboarding and training: New technicians can immediately understand what scope they are operating in without needing tribal knowledge or warnings.
Improved confidence and speed: Technicians can move faster without second-guessing whether an action is global or tenant‑specific.
Clearer mental model of CIPP: Explicit scope signalling reinforces how CIPP separates global configuration from tenant execution.

Value or Importance

This is a UX safety and usability improvement rather than just a cosmetic change.

CIPP is increasingly powerful, and with that power comes the need for clear scope boundaries. Making scope explicit in the UI helps prevent high‑impact mistakes, aligns with MSP operational realities, and improves the experience for both new and experienced users.

Given CIPP’s role as a centralized, multi‑tenant control plane, scope clarity is critical.

Proposed UI Approaches

Any one of the following would significantly improve clarity without changing existing workflows:

Visual Styling

Global items displayed with a subtle but distinct style (e.g., different text color, bolding, or background accent)
Tenant‑scoped items retain current styling-

Icon or Badge

Small, consistent icon (e.g., 🌐 or similar) next to global menu items
Optional tooltip: “This action applies globally across tenants.”

Scope Labeling

Inline label such as (Global) or (Tenant) next to menu entries
Especially helpful in mixed sections like Identity Management

Contextual Warning (optional enhancement) in the UX page along with a menu enhancement above)

Lightweight notice/banner when entering a global section while a tenant is selected: “You are editing a global configuration, not the selected tenant.”

These options are intentionally lightweight and do not require restructuring the navigation or relocating features.

PowerShell Commands (Optional)

No response

Originally created by @Lowell-Syncrety on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5404 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement CIPP currently mixes global and tenant‑scoped functionality within the same navigation sections, which is logical from a workflow perspective but not visually obvious to the operator. For example, under Identity Management → Administration, tenant‑specific items like Users and Groups appear alongside Group Templates, which are global in scope. While the placement makes sense functionally, there is no visual indication that actions taken in Group Templates affect all tenants rather than the currently selected tenant. This creates confusion, particularly for: - New technicians - Junior staff - Anyone working quickly under the assumption that the selected tenant context applies to all nearby actions The risk is not theoretical: modifying a global object while believing you are operating tenant‑locally can result in unintended cross‑tenant impact. As an admin myself I'm still running into this and have to double-check other clues in the resulting UX page to make sure I'm doing something global or tenant-specific. ### Benefits for MSPs - Reduced operational risk: Clear scope indicators help prevent accidental global changes when a technician believes they are working within a single tenant. - Faster onboarding and training: New technicians can immediately understand what scope they are operating in without needing tribal knowledge or warnings. - Improved confidence and speed: Technicians can move faster without second-guessing whether an action is global or tenant‑specific. - Clearer mental model of CIPP: Explicit scope signalling reinforces how CIPP separates global configuration from tenant execution. ### Value or Importance This is a UX safety and usability improvement rather than just a cosmetic change. CIPP is increasingly powerful, and with that power comes the need for clear scope boundaries. Making scope explicit in the UI helps prevent high‑impact mistakes, aligns with MSP operational realities, and improves the experience for both new and experienced users. Given CIPP’s role as a centralized, multi‑tenant control plane, scope clarity is critical. ### Proposed UI Approaches Any one of the following would significantly improve clarity without changing existing workflows: **Visual Styling** - Global items displayed with a subtle but distinct style (e.g., different text color, bolding, or background accent) - Tenant‑scoped items retain current styling- **Icon or Badge** - Small, consistent icon (e.g., 🌐 or similar) next to global menu items - Optional tooltip: “This action applies globally across tenants.” **Scope Labeling** - Inline label such as (Global) or (Tenant) next to menu entries - Especially helpful in mixed sections like Identity Management **Contextual Warning (optional enhancement) in the UX page along with a menu enhancement above)** - Lightweight notice/banner when entering a global section while a tenant is selected: “You are editing a global configuration, not the selected tenant.” These options are intentionally lightweight and do not require restructuring the navigation or relocating features. ### PowerShell Commands (Optional) _No response_

kerem added the

labels

2026-03-02 13:53:41 +03:00

kerem commented

2026-03-02 13:53:42 +03:00

Author

Owner

@Lowell-Syncrety commented on GitHub (Feb 19, 2026):

Forgot to note... There are menu items that default to applying to the selected tenant, but also provide the capability of applying multi-tenant. I don't think these would need to be separately identified, but if using an icon (e.g., the globe icon for global sections) some sort of "multi-tenant" icon could be used.

@Lowell-Syncrety commented on GitHub (Feb 19, 2026): Forgot to note... There are menu items that default to applying to the selected tenant, but also provide the capability of applying multi-tenant. I don't think these would need to be separately identified, but if using an icon (e.g., the globe icon for global sections) some sort of "multi-tenant" icon could be used.

kerem commented

2026-03-02 13:53:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 1, 2026):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Mar 1, 2026): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2603

No description provided.

Rows
Columns