Hi there fellow Atlassian guru's!
I'm comming across a specific use case in setting up a new scheme in Assets. See if you can help me out!
1: Mask Attributes
One of the objectTypes included in the scheme are 'licenses', containing the attribute 'License key'. Now you can imagine this values can be marked as sensitive. So i was wondering if it would be possible to restrict the access to the value, or show it as masked?
2: Hide objects
Our scheme will cover multiple business units, with their own teams maintaining their assets on the same scheme. By default, whan access is provided to the scheme, all objects within that scheme become visible for that user.
I was wondering how i can set up the roles to provide access to the scheme but only provide access to a subset of objecttypes.
In extend, I would need to be able to dictate the security level on Object level.
This is not an option in assets for both questions.
Roles can be set on schema and object type level.
The only option you will have is to prove each business unit with its own schema.
The same applies to any DB, you can restrict viewing and/or editing of tables by roles, but not on a subset of the data that is in a table.
Also hiding information from an object (row in a DB is not possible).
Relational DB's like SQL or Oracle will have the option to create views based on table data, but still then row access can be applied, but there is no column restrictions to be set.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.