Allow SCIM provisioning at organization level with multi-project user mapping #80

Closed
opened 2026-04-05 16:18:49 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @atippin1 on 2/17/2026

Is your feature request related to a problem? Please describe.
Currently, SCIM (System for Cross-domain Identity Management) configuration must be set up separately for each project in OneUptime. This means that organizations with multiple projects need to repeat the entire SCIM setup process for every single project, which is time-consuming, error-prone, and creates unnecessary administrative overhead.

Describe the solution you'd like
SCIM should be configured at the organization/account level, outside of individual projects. This would allow administrators to:

  • Set up SCIM integration once at the organization level
  • Provision users and groups from their identity provider (IdP) centrally
  • Map or assign provisioned users and groups to specific projects as needed
  • Manage user provisioning from a single location rather than within each project

This approach would provide a centralized identity management experience where SCIM acts as the single source of truth for user provisioning across all projects.

Describe alternatives you've considered
Maintaining the current per-project SCIM setup but adding the ability to duplicate/clone SCIM configurations across projects
Creating SCIM configuration templates that can be quickly applied to new projects

However, these alternatives still don't solve the fundamental issue of having SCIM live within projects rather than at a higher organizational level.

Additional context
This feature would align with how most enterprise SaaS platforms handle user provisioning, where SCIM/SSO is configured once at the organization level and then users are assigned to specific workspaces, teams, or projects. It would significantly improve the onboarding experience for enterprise customers and reduce the administrative burden for managing multi-project environments.

*Originally created by @atippin1 on 2/17/2026* **Is your feature request related to a problem? Please describe.** Currently, SCIM (System for Cross-domain Identity Management) configuration must be set up separately for each project in OneUptime. This means that organizations with multiple projects need to repeat the entire SCIM setup process for every single project, which is time-consuming, error-prone, and creates unnecessary administrative overhead. **Describe the solution you'd like** SCIM should be configured at the organization/account level, outside of individual projects. This would allow administrators to: - Set up SCIM integration once at the organization level - Provision users and groups from their identity provider (IdP) centrally - Map or assign provisioned users and groups to specific projects as needed - Manage user provisioning from a single location rather than within each project This approach would provide a centralized identity management experience where SCIM acts as the single source of truth for user provisioning across all projects. **Describe alternatives you've considered** Maintaining the current per-project SCIM setup but adding the ability to duplicate/clone SCIM configurations across projects Creating SCIM configuration templates that can be quickly applied to new projects However, these alternatives still don't solve the fundamental issue of having SCIM live within projects rather than at a higher organizational level. **Additional context** This feature would align with how most enterprise SaaS platforms handle user provisioning, where SCIM/SSO is configured once at the organization level and then users are assigned to specific workspaces, teams, or projects. It would significantly improve the onboarding experience for enterprise customers and reduce the administrative burden for managing multi-project environments.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#80