You can control how a transaction is seen by different members of your organisation via transaction settings.
Search & Home area visibility
- Private: Select this option when you want to restrict visibility of a transaction to only those members of your organisation who are directly working on it. With this option selected, nobody outside the transaction team will see it in their home area or search results. This is a good choice if the work is sensitive or if contractual requirements mean information disclosure is on a need to know basis.
- Visible with permission: This makes the transaction visible to anyone in your organisation who has been given permission to view non-private transactions. This is a good option if the transaction content is not sensitive and your colleagues would benefit from knowledge of the project.
When Search & Home area visibility is selected, a special read-only role called Internal viewer is automatically added the transaction
The Internal Viewer role can only see the dashboard and risk review pages of a transaction. Access to the risk review is limited to read-only and cannot be upgraded to have write permissions.
The list of users who appear in the Internal Viewer role is made of all organisation members who have been given permission to see non-private transactions (see Granting permissions to see non-private transactions below).
Whenever you change the Search & Home area visibility back to private, the Internal Viewer role and associated access it automatically removed.
Templating
Enabling templating means that the structure and content of a transaction is available for others in your organisation to duplicate and reuse. This opens up the possibility of generating standard templates for due diligence work which can lead to significant time saving and improved consistency. Templating options are:
- None: Nobody can template this transaction. Select this option if the content is confidential and should not be duplicated by others.
- Transaction team: Only colleagues assigned to a transaction role can template it. In other words, only those working directly on the transaction can duplicate the content elsewhere. This offers a balanced approach that restricts sharing to those who are already familiar with the content.
- Org-wide: Anyone in your organisation can template the transaction. This option is ideal for standardised templates and content that you want shared across your organisation.
The above visibility settings apply only to users inside your organisation. Users outside of your organisation (e.g. Clients) can never see internally shared transactions.
Setting visibility when creating a new transaction
Search & Home page visibility and templating settings must be selected when you create a new transaction.
These initial settings can be edited at any time via the transaction settings tab.
Identifying private transactions
You can spot a private transaction by the lock icon displayed in the home area and in the transaction header
Viewing shared transactions
The home page provides two tabs for viewing transactions:
- My Transactions: This list shows only the transactions you are directly working on i.e. where you have an internal role assigned.
- All: This list shows all the transactions you are working on AND any non-private transactions that have been shared by others in your organisation. If you do not see the All tab then your organisation role does not have permission to see non-private transactions.
Granting permission to see non-private transactions
Organisation administrators can control who has permission to see non-private transactions via the Roles and permissions page.
The View non-private transactions permission can be granted to any role in your organisation. Note that the Administrator role has this permission on by default.