Before a user can see a SlicerDicer data model, they must have a security class that grants access to it. Each model is protected so that people see only the subjects relevant to their role, and administrators give access by assigning the appropriate class to the user or their role. This is the third option. Radar configuration is a separate framework for building dashboards and has no bearing on which models a user can view. There is no SlicerDicer tab in the Dashboard Editor that controls model access; the Dashboard Editor is used to build dashboards and not to administer analytic tools. A session shared by an administrator would let a user open that specific session, but it does not provide access to the data model in general, and the recipient would still need the underlying access to see results. The principle that access depends on security classes applies across the Cogito applications. When a user cannot find a model, the administrator ' s first step is to compare their classes with those of a colleague who can see it and to request the missing class through the usual approval process.
[Reference: Cogito Fundamentals – SlicerDicer: Data Model Security Classes, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit