-
Enter information for Users. Columns A and B are required.
-
Copy the formulas in Column G down the rows as needed.
-
Copy the XML content of column G into Notepad as a .XML file. Make sure the header and footer match.
-
Import the file into the application and confirm the users are visible.
Data_Certifier Security Design
This template organizes entities into Workflows and then identifies which users load data and which users certify data for each Workflow.
-
In the Entity field, define all Entities that submit and report data.
-
In the Workflow field, add the Workflow Name, which identifies which Workflow is responsible for loading data for the respective Entity.
-
For each Entity/Workflow combination, define the users who will load and certify data.
WF Profile Security Design
-
In Column A, define the Workflows that need Workflow security groups.
-
In Column B, define the naming convention of the Workflow security groups.
-
Enter the appropriate users and groups for the Workflows.
-
Copy XML from column AH to an .XML file and load it into the application.
Entity Security Design
-
In Column A, define the Entities.
-
In Column B, define the naming convention for the Entity Read and Read/Write Security Group.
-
In Column C, add the description of the Entity Security Groups.
-
For the Child columns, enter either the User or Group assigned to the Entity Read or Read Write Security Group.
Read Only Example: For the Entity Read Security Group, enter the users who require access but do not have access to the Entity through a Workflow. If a user does not load data but has workflow responsibility through a Review Workflow, then assign the Review Workflow Data Execution group or Review Workflow Access Group to the Entity Read Security Group.
Read/Write Example: For the Entity Read Write Security Group, assign the Workflow Data
Execution Groups to the Entity Read Write Group. By gaining access to the Workflow Data Execution Group, you would then have access to the Entity Read Write Security Group for data loading. Maintenance of user data loading is then controlled by which workflows they are allowed access to.
It is recommended to start from the top of the Entity Hierarchy and continue toward the bottom. Create the Entity Security Group prior to assigning it to other Entity Security Groups.
5. Copy XML from column AS to a text file and load to the application.
Account Security Design
There is no Read or Read-Write security with Account members. To access Account security, go to Cubes > Data Access This is known as slice security.
The Account Security Design allows organization for accounts that require security and users who have access to them. There is currently no XML builder.
