We are a company providing connected services leveraging operational data to our customers.
Enable us to provision OCS Tenants on behalf of our customers, and manage things like data ingress, stream configuration, data mapping, context, and others for our customer managed accounts SO THAT our customers can just consume our service (and they paid for us to do these types of tasks).
We need a way to onboard our customers easily with their own OCS tenants SO THAT we can expand our business to all our potential customers, not just those that already have a relationship with OSIsoft.6 votes
This work is planned as part of our Community & stream data sharing functionality in OSIsoft Cloud Services (OCS). It will likely come after we release our initial data sharing functionality.
As an account admin for OCS in my company, I need to bulk-add users and their permissions level to OCS so that it's easy to get all my users onboard quickly.
Users should receive an invitation email, temporary password to reset (if needed), or instructions of how to log in via an existing identity provider. These invitations should expire after a period of time.3 votes
Currently, I must use a Microsoft IdP (MSA) account to accept the OCS invitation. If I ultimately want to use another IdP (e.g. Google), this means I have to temporarily create a MSA account just to accept the invitation. I would like to directly use my non-MSA account to accept the invitation.2 votes
Ability to bookmark a URL, e.g. https://cloud.osisoft.com/alias, where opening that URL would automatically associate with my tenant. Clicking to sign in, the browser would know to use my alias, even if I have not checked the box to remember my tenant. This could be useful across devices, across browsers, or in private browsing.1 vote
Ability to configure a lightweight OCS Account with limited resources (namespaces, streams, etc.), potentially only for user management and consuming data shared through communities.1 vote
- Don't see your idea?