File and Folder Properties
This applies to: Managed Dashboards, Managed Reports
Each item you create in Managed Dashboards and Reports is treated as a file, including data connectors, metric sets, and dashboards, as organized into folders and projects.
The Properties dialog lets you view and edit the properties associated with a selected file, folder, or project. You can view the references to and from a file, modify security settings, and roll back to a previous version in the revision history.
Launch the Properties Dialog
To launch the Properties dialog, select a file, folder, or project when opening a file from the Explore window or another file explorer. Right-click (or long-tap) and select Properties from the context menu that appears.
Properties You Can View and Edit
The Properties dialog lets you view and edit the following properties:
Name - Rename the item.
Description - Add your own descriptive text, displayed in the item's tooltip.
Tags - Add tag words to help categorize your files and find them when searching.
Add or Remove Tags
To add a tag to the file or folder, just type a word in the Tags box and press the Enter or Space key. You can also use the auto-complete menu that appears as you type to select an existing tag in the system.
You can remove a tag by clicking the x button beside the tag (unless the tag is inherited for a file from one of its containing folders).
Once you've added tags, you can search by them in the Explore window on many screens or in other file explorers such as in Open dialogs. Files can be found by the tags set either on the file, or one of its containing folders.
Read-Only Properties
Further down are various read-only properties:
ID
Location
Type
Subtype
Created By
Created Time
Last Modified Time
Checked Out To - (if applicable)
The ID property is needed when writing scripts that reference items such as a metric set or dashboard.
Revision History
Revision history is the version control mechanism built-in to Symphony. Scroll all the way down in the Properties dialog, and then select Revision history.
The Revision History dialog lists all of the revisions or changes that happened to this item. Each revision corresponds to a check in by a specific user, or an event such as the initial file creation. For more information about checking in items, see Check In, Check Out and Auto Saving.
Roll Back To a Previous Revision
From the Revision History dialog, you can roll back the file to a previous revision by clicking the corresponding button in the Roll Back column. This is useful if, for example, you are not happy with recent changes made to a dashboard and you want to revert it to an earlier state.
In the revision history, select the Roll Back button that corresponds to the revision you want to go back to.
The current file will be checked out if necessary, updated with the contents of the chosen revision, and then checked in automatically. This will create a new revision for the file.
References To and From the File
Scroll all the way down in the Properties dialog, and then click References to see a list of other items that reference (i.e., have a dependency on) the current file, and items that the current file itself references (i.e., references by this file).
This can show the data lineage, tracing the data displayed in a dashboard back through each item to its source, or vice versa.
Show Recursive References
By default, only direct references to and from the current file (e.g., data cube) are shown. If you want to see all references (including references to references), select the Show Recursive References option. For example, use this option to find out what data connectors are ultimately being used by a dashboard where a data cube and metric set are also used.
Security Privileges
To set security privileges on the file, folder, or project, click Security at the bottom of the Properties dialog.
The Security dialog presents a list of tenants and groups. For each tenant or group, you can allow or deny various privileges (e.g., Read, Write, Delete).
Note: The Full Control privilege is required on an item to change its security privileges unless you are an administrator. Full Control is automatically granted to the account that created it but can be removed afterward if needed.
Inheritance
Security privileges set on a folder or project are inherited by default by the files contained within it, allowing you to configure security for all of its contained files at once. To create new subfolders, right-click a folder and choose New Folder, then right-click files to Cut and right-click a folder to Paste, or drag selected files while holding the Shift key on the keyboard.
The check boxes in the Security dialog determine whether files inherit privileges from their parent or not:
The Inherit Privileges check box determines whether this file or folder inherits privileges from the file or folder containing it. When a privilege is inherited, a blue information icon appears that you can click to find out where it was set.
Select Replace Explicitly Set Privileges On Children to make all files and folders contained within this one inherit the privileges you are setting. This check box takes effect when the dialog is submitted and will not remain checked if you return later, instead it clears any explicitly set privileges on contained files or folders so that they inherit from their parent.
List of Security Privileges
| Privilege | Description | Remarks |
|---|---|---|
The privilege to delete a file. |
|
|
The privilege to execute a file. |
This privilege has to be granted on anything that acts as a data source:
For example: to use a metric set, the underlying data cube, data connector, and tables must have at least an Execute privilege.
Note:
A manual select ignores the privileges on the native structure of a data connector (tables, views, etc.).
|
|
The privilege to fully control a file, folder, or project. |
Full Control implies everything, including changing security privileges – meaning when this privilege is inherited from the containing folder or project, it implies that Full Control is granted regardless of other settings. For example, granting this privilege on a project automatically implies that the assignee of the privilege is a "project administrator" who implicitly has the Full Control privilege granted on anything contained in it. |
|
The privilege to list all items in a folder. |
Read is implied by List Folder Contents. |
|
The privilege to modify a folder's properties and create child items. |
Read is implied by Modify Folder. |
|
The privilege to see a file and its contents. |
Execute is implied by Read. |
|
The privilege to update the contents of a file. |
Read is implied by Write. |
Add a User, Group, or Tenant to the List
To give privileges to a user, group, or tenant, you need to add it to the Groups and Accounts list.
Select Add... if needed to add them to the list. A Select Accounts or Groups dialog opens, allowing you to filter all user accounts and groups by selecting a tenant. Search or scroll to select groups and user accounts. Select Save to return to the Security dialog and assign privileges.
Click the delete icon to the right of a user account or group in the list if you want to stop setting privileges for it directly on this file or folder.
Important: You must give file privileges for each group when you return to the list.
Give File Privileges To a User Account or Group
Select a user account or group under Groups and Accounts on the left, and then set Allow or Deny for each type of privilege listed on the right. When you have completed your selections, select Save.
If you assign Deny to a privilege for a user, a user's group, or a tenant to which a user belongs, it will always take precedence over any other Allow assignment for that user for that privilege. You must remove the Deny assignment on that privilege for the user, then add an explicit Allow for that user, group, or tenant.
Note: Administrators, system administrators and users with full control of the containing project or folder have all privileges and are not effectively denied any privilege.
Note: Privileges set on a user account, group, or tenant may remain listed even after the user, group, or tenant is deleted from Symphony: deletion does not automatically remove privileges assigned to them.
For more information, see:
Comments
0 comments
Please sign in to leave a comment.