Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Appendix A: Sizing and Platform Requirements
  9. Appendix B: Application Components
  10. Appendix C: IDD Security Configuration
  11. Appendix D: Data Security
  12. Appendix E: Example Role-Based Security Configuration
  13. Appendix F: Data Masking
  14. Appendix G: Siperian BPM Workflow Engine
  15. Appendix H: Locale Codes
  16. Appendix I: Troubleshooting
  17. Appendix J: Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Object and Column Security

Object and Column Security

SAM provides role-based security privileges on design objects and columns defined in an ORS.
An IDD application uses this security configuration so that the data that is shown, and the operations that are available to an individual user, depend on the role(s) assigned to that user account. IDD application users see only the data and functionality to which they have been granted access. For example, if a user does not have READ access to the HISTORY table for a base object, in the IDD application, the History command for that subject area is not available to the user.
A Hub user with Administrator access (configured in the Users tool in the Hub Console) is a super-user for IDD and has full privileges on all objects.

0 COMMENTS

We’d like to hear from you!