|
Modern apps need to be responsive to meet specific user needs - long gone are the days of one interface for all users.
The mydigitalstructure service includes a number of different mechanisms that an app can use to respond to a user based on their role.
|
 |
| View |
You can alter the view based on the user roles assigned to a user.
CORE_GET_USER_DETAILS returns a roles object that can be used to share the User Experience/Interface. |
| Functionality (Controller) |
User roles can be set up by the system administrator / developer. Each user role can be assigned restricted access to each of the functional mydigitalstructure methods. |
| Data Access (Model) |
Data within the mydigitalstructure model/service can be protected in a number of ways:
- Property based, including specific values
- User role based
- Based on the contacts relationship manager
- Project teams
|
|
DATA ACCESS,
USER ROLE CONTROLS |
| User Role |
By default all data is accessible to any user that has functional access to it.
To restrict access to specific object data use SETUP_ROLE_OBJECT_ACCESS_MANAGE.
You can control the users (via the user role) ability to search for or update/manage specific data.
Currently it is restricted to custom structure data.
|
|
DATA ACCESS,
CONTACT RELATIONSHIP MANAGER CONTROLS |
| Overview |
 |
| User |
Use SETUP_USER_MANAGE &relationshipmanagersecuritytype= to enable.
- None (1)
- Standard (2)
- Tight (3)
|
| Types |
Standard
Can only see contacts (business/person) that:
- the user is the relationship manager for.
- the user is a secondary relationship manager for.
- that the user is a manager (setup with SETUP_USER_MANAGER) of the user as per a & b above.
- are linked to a user with in the same space
Tight
Is the same as standard but without the option d. (ie the ability to access internal contacts linked to users) and also linked other objects
|
| Relationship Manager |
A contact (business/person) can have multiple relationship managers. |
|
