Did You Know?
Spitfire allows users (who have the proper permission) to mark documents and their attached files as “confidential.” With one exception*, confidential documents can be opened only by those to whom the document has been explicitly routed, effectively cancelling the generic PAGE | Document Access permission for other users. For example, if Betty has permission to read all Issue documents, and a PM routes a confidential document to Wilma but not Betty, Wilma will be able to open the document but Betty will not.
The Confidential Flag
- In Power UX, the Confidential checkbox appears on the left side panel. If the checkbox is not visible by default, you can make it visible through the gear icon. (A System Admin could also make the checkbox visible as part of the Default Site Settings.)
- In Classic UI, the Confidential checkbox appears at the bottom of the Route Detail tab.
Notes:
- When a document is marked confidential, all file attachments on the document are marked confidential at the same time. This means that files on a confidential document can only be viewed/opened by the people on the route (unless a user has the LIST | Can Read All Files capability). To continue our example above, Betty–who does not have the LIST | Can Read All Files capability in her roles–would not be able to look at any attached confidential files, even from the Catalog or project Files part.
- A user with the LIST | Can Read All role capability would be able to view confidential files but still not be able to open a confidential document that was not routed to them.
- Only the creator of a confidential document can add people to the route. All other editing of the document follows the standard collaborator rules.
- *The exception: A user with S permission on the SYS | Global Access capability (for example, a Sys Admin) can access confidential documents.