--- title: Input Visibility description: Manage who can view each input in the 'Manage Input Visibility' section of the input detail screen. --- [Skip to content](https://knowledge.triaster.co.uk/manage-input-security#main-content) [Contact Support](https://knowledge.triaster.co.uk/kb-tickets/new) [![triaster-logo-hex.svg\]](https://knowledge.triaster.co.uk/hubfs/TRIASTER/img/triaster-logo-hex.svg)](https://www.triaster.co.uk/) - [Knowledge Base Home](https://knowledge.triaster.co.uk/) Open main navigation Close main navigation - [Knowledge Base Home](https://knowledge.triaster.co.uk/) - [Contact Support](https://knowledge.triaster.co.uk/kb-tickets/new) Welcome. How can we help you? - There are no suggestions because the search field is empty. 1. [Triaster Knowledge Base](https://knowledge.triaster.co.uk/) 2. [Process Execution Pack - Ask The Crowd](https://knowledge.triaster.co.uk/process-execution-pack-ask-the-crowd) 3. [Getting Started](https://knowledge.triaster.co.uk/process-execution-pack-ask-the-crowd#getting-started) # Input Visibility ## Manage who can view each input in the 'Manage Input Visibility' section of the input detail screen. Only an input's **Owner** can manage input visibility.  An input's owner is the person who is ultimately accountable for that input's progress to closure. When an input is submitted it must be assigned an owner; if you are the only process owner for a crowd then all inputs will be automatically owned by you. If there is more than one process owner, the moderator must assign the input to the appropriate owner.  Managing an input's security is different depending on if it is an input you have submitted, or one you have not submitted: - [Managing the security of an input you have submitted](https://knowledge.triaster.co.uk/manage-input-security#one) - [Managing the security of an input you have not submitted](https://knowledge.triaster.co.uk/manage-input-security#two) ### Managing the Security of an Input you have Submitted: - As an owner as soon as you have submitted a new input you are taken to the **Input Detail** screen. ![Screenshot 2021-08-24 at 15.05.28](https://knowledge.triaster.co.uk/hs-fs/hubfs/TRIASTER/img/Knowledge%20Base/Screenshot%202021-08-24%20at%2015.05.28.png?width=600&name=Screenshot%202021-08-24%20at%2015.05.28.png) - When you submit an input it is **Locked** which means that only Moderators, the inputs owner, and you, the person who has submitted the input, can see it. - Click **Unlock this Input** to manage who can see the input. The visibility settings are automatically set to **Users**, but this can be easily changed. ![Screenshot 2021-08-24 at 15.19.54](https://knowledge.triaster.co.uk/hs-fs/hubfs/TRIASTER/img/Knowledge%20Base/Screenshot%202021-08-24%20at%2015.19.54.png?width=655&name=Screenshot%202021-08-24%20at%2015.19.54.png) - Select who you would like to view the input from the options available in the **Manage Input Visibility** box at the top right-hand side of the screen. Check the tick box to select who can view the input. The roles built-in to ATC are as follows. Bespoke roles with customised permissions can also be set up. | Built-in Roles | Permissions and Purpose | | --- | --- | | Moderators | Moderators are able to moderate any inputs for their crowd. Their role is to review all inputs as they are received, edit them if required, delete them if appropriate, and allocate them to the correct process owner. | | Public | The Public is everyone in the world. Permissions cannot be granted to the Public, who are best thought of as a security group. If you want to make an input entirely public, so that *everyone* is able to view it, set it's input security to **Public (Everyone in the World)**. | | Process Owners | A Process Owner should be thought of as the person who is accountable for the inputs which are assigned to them. The buck stops with them. | | Users  | Users are all crowd members. As with the Public, permissions cannot be granted to 'Users' who are again best thought of as a security group.  If you want to make an input visible to everyone in the Crowd, set it's input security to **Users (All Crowd Members)**'. | - Click **Save Changes** to save the new security settings. - If at any point you wish to Lock the input again simply click the **Lock This Input** button. ### Managing the Security of an Input you have not Submitted: - Click on the **Inputs** menu option found at the top right-hand side of the screen. - By default the input's **List View** will display. - Select the relevant input - you can do this by searching using the **Search Filters** on the left-hand side of the screen. - Click on relevant input's title to open its **Input Detail** screen. ![Screenshot 2021-08-24 at 15.05.28](https://knowledge.triaster.co.uk/hs-fs/hubfs/TRIASTER/img/Knowledge%20Base/Screenshot%202021-08-24%20at%2015.05.28.png?width=655&name=Screenshot%202021-08-24%20at%2015.05.28.png) - When an input is first submitted it is **Locked** which means that only Moderators, the input's Owner and the person who has submitted the input, can see the input. - Click **Unlock this Input** to manage who can see the input. The visibility settings are automatically set to **Users** but this can be easily changed. ![Screenshot 2021-08-24 at 15.19.54](https://knowledge.triaster.co.uk/hs-fs/hubfs/TRIASTER/img/Knowledge%20Base/Screenshot%202021-08-24%20at%2015.19.54.png?width=655&name=Screenshot%202021-08-24%20at%2015.19.54.png) - Select who you would like to view the input from the options available in the **Manage Input Visibility** box at the top right-hand side of the screen. Check the tick box to select who can view the input. The roles built-in to ATC are as follows. Bespoke roles with customised permissions can also be set up. | Built-in Roles | Permissions and Purpose | | --- | --- | | Moderators | Moderators are able to moderate any inputs for their crowd. Their role is to review all inputs as they are received, edit them if required, delete them if appropriate, and allocate them to the correct process owner. | | Public | The Public is everyone in the world. Permissions cannot be granted to the Public, who are best thought of as a security group. If you want to make an input entirely public, so that *everyone* is able to view it, set it's input security to **Public (Everyone in the World)**. | | Process Owners | A Process Owner should be thought of as the person who is accountable for the inputs which are assigned to them. The buck stops with them. | | Users  | Users are all crowd members. As with the Public, permissions cannot be granted to 'Users' who are again best thought of as a security group.  If you want to make an input visible to everyone in the Crowd, set it's input security to **Users (All Crowd Members)**'. | - Click 'Save Changes' to save the new security settings.    - [Glossary](https://knowledge.triaster.co.uk/glossary) - [Getting Started](https://knowledge.triaster.co.uk/getting-started) - [Implementing](https://knowledge.triaster.co.uk/implementing) - [Optimising](https://knowledge.triaster.co.uk/optimising) - [FAQs](https://knowledge.triaster.co.uk/faqs) - [Language Pack - Business Phrasebook](https://knowledge.triaster.co.uk/language-pack-business-phrasebook) - [Process Execution Pack - Ask The Crowd](https://knowledge.triaster.co.uk/process-execution-pack-ask-the-crowd#main-content) - [Glossary](https://knowledge.triaster.co.uk/process-execution-pack-ask-the-crowd#glossary) - [Getting Started](https://knowledge.triaster.co.uk/process-execution-pack-ask-the-crowd#getting-started) - [Implementing](https://knowledge.triaster.co.uk/process-execution-pack-ask-the-crowd#implementing) - [Optimising](https://knowledge.triaster.co.uk/process-execution-pack-ask-the-crowd#optimising) - [Process Library On-premises](https://knowledge.triaster.co.uk/process-library-on-premises) - [Process Navigator](https://knowledge.triaster.co.uk/process-navigator) - Home - Products - Pricing - Blog - Company [![triaster-logo](https://knowledge.triaster.co.uk/hubfs/TRIASTER/img/triaster-logo.svg "triaster-logo")](https://www.triaster.co.uk) Copyright © 2026, Triaster Limited