Ability to restrict user access to an Tenant's Users and namespaces within a Tenant so that certain users/roles don't know other users in the tenant.
Used for scenarios when a Tenant is storing multiple customer's access within the same Tenant prior to Community Data Sharing services being available.15 votes
We have implemented a new feature in OCS called ‘strict mode’ that can be enabled by OSIsoft on a customer’s tenant. This feature is now in preview.
Enabling strict mode hides several OCS portal menus, API routes, and tiles on the landing Dashboard to non-Admin users.
The feature is intended for use for tenants that may have multiple company’s users logging into the tenant (example: connected services and their customers) and there is a need to hide administrative information and other user information from non admin users.
Strict mode hidden menus include: Identity Providers, Users, Roles, Groups, Clients, Usage, Health, My profile only shows a user’s own information. Likewise, API routes goes to a forbidden error. Dashboard tiles hidden include: usage tile, health tile, quick links tile.
To enable strict mode, please contact OSIsoft and we can enable it on your tenant. Please let us know your feedback.
We don't have the resources or skills to setup, administer, and manage our own PI System. We would just like to be able to use a hosted system delivered as Software as a Service (SaaS).10 votes
OCS is a hosted cloud data store and is being built to support remote operations monitoring scenarios.
- Don't see your idea?