User setup
| The content of this website is last updated to F2 version 11. cBrain are working hard on supplying you with the newest documentation of F2. |
The "User setup" report type extracts data about which users were assigned which roles, by whom, and when. This enables monitoring of unintended user access.
The report type has two default configurations based on changes to F2’s users made by user administrators.
The "Standard" default configuration
Use the "Standard" default configuration to get a detailed insight into changes to F2’s users.
The configuration contains neither filters nor fields to fill in.
| Column name | Description | Examples |
|---|---|---|
Date and time |
The full timestamp with year, month, day, hour, minute, and second. |
2023-11-14T12:40:29.597 2023-04-12T15:30:20.773 |
Action |
Name of the action that was performed. |
UserUpdated MembershipRemoved |
Username |
The value indicated in the "Name" field in the user properties. |
Holly Rogers Isaac Johnson |
Role’s unit |
The unit with which the role is associated. |
HR Administration |
Role’s unit location |
Path for the unit with which the role is associated. |
/Doc Organisation/Dok Authority/Administration/IT office |
Role name |
Name of the affected role as specified under "Role type" in the "Roles and privileges" window. |
Caseworker Can delete everything on cases |
Updated property |
The setup property that a given action has changed. |
Name LimitedUserAccess |
Before |
A property, attribute, or field’s old value before an action. In this case, it is the value of the property mentioned in "Updated property". |
Hannah Hendricks true |
After |
A property, attribute, or field’s new value after an action. In this case, it is the value of the property mentioned in "Updated property". |
Penelope Poole false |
Name |
Name of the user who has performed an action. If the action was performed on behalf of another user, the name of the "on behalf of" user is specified. |
Holly Rogers Isaac Johnson |
Login name |
If a user has performed the action on behalf of another user, the name of the logged-in user is specified. |
Holly Rogers Isaac Johnson |
The "Roles" default configuration
Use the "Roles" default configuration to create extractions that specifically show allocation and removal of roles to users.
The configuration contains filters, but no fields to fill in.
| Column name | Description | Examples |
|---|---|---|
Date and time |
The full timestamp with year, month, day, hour, minute, and second. |
2023-11-14T12:40:29.597 2023-04-12T15:30:20.773 |
Action |
Name of the action that was performed. |
MembershipCreated MembershipRemoved |
Username |
The value indicated in the "Name" field in the user properties. |
Holly Rogers Isaac Johnson |
Role’s unit |
The unit with which the role is associated. |
HR Administration |
Role’s unit location |
Path for the unit with which the role is associated. |
/Doc Organisation/Doc Authority/Administration/IT Office |
Role name |
Name of the affected role as specified under "Role type" in the "Roles and privileges" window. |
Caseworker Can delete everything on cases |
Name |
Name of the user who has performed an action. If the action was performed on behalf of another user, the name of the "on behalf of" user is specified. |
Holly Rogers Isaac Johnson |
Login name |
If a user has performed the action on behalf of another user, the name of the logged-in user is specified. |
Holly Rogers Isaac Johnson |
Filters
When drawing a report with this default configuration, the extraction is filtered as described in the table below.
| Filter | Value | Effect |
|---|---|---|
Role name |
Is not empty |
The "Role name" column is only filled in if an action allocates, changes, or removes a role from a user. This way all actions related to roles are included, while all other actions are excluded from the extraction. |
Other available columns
The following table covers columns that are accessible when configuring reports, but are not included in the default configurations.
| Column name | Description | Examples |
|---|---|---|
Operation type |
The unique action ID |
24 32 |
Participant ID |
The unique user ID for the participant affected by the action. |
107 124 |
User ID |
The unique user ID of the user who has performed an action. If the action was performed on behalf of another user, the unique user ID of the "on behalf of" user is specified. |
107 124 |
Login user ID |
If a user has performed the action on behalf of another user, the unique user ID of the logged-in user is specified. |
107 124 |
Count |
Accumulates identical rows in the data extract and returns the total. |
249 |