Share
ReportI have a custom "defect tracking" entity in my organization's default BU. It's intent is to be a central repository for users from any child BU to report a defect. Each BU will have their own records. Users from each BU should only be able to access the records owned by users in their BU.
I have created a six-paned Dashboard that mimics a Kanban Board. Top left is NEW, then UP NEXT, then DEV, then TEST, then QA, then ready for RELEASE.
A subset of users are IT, so need the ability to see and work with the records from all the BUS.
Here is what I'm thinking:
- Each BU will have its own Dashboard with Views filtered by the record owner's BU.
- A Team will live in each BU where all the IT users are members. That Team has a BU depth security role on the defect entity. This means the IT users will be in many teams and have access to records owned by all BUs.
- The records created in each BU will be owned by the BU user until it gets assigned to the IT Team. There is another lookup to User on the entity for an "IT Assigned To" field. This keeps that assignment out of the security circle.
Does this sound like the best way to accomplish having one set of users with access to records across all BUs and another set of users with access to only records in their BU?
*This post is locked for comments
All responses (
Answers (
34,475
