{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":34657,"path":"mobile/attachment-source-define.md","title":"Define attachment sources available to users","bundle":null,"doc_type":null,"release":"australia","body":"\n# Define attachment sources available to users\n\nControl the origin of where images and files are sourced from, including a phone's gallery, camera, or file system. This capability confirms that images can’t be reused and verifies that they aren't AI-generated.\n\n## Before you begin\n\nRole required: admin\n\n## About this task\n\nYou can limit the origins of attachments to ensure that images are sourced from one or all of the following:\n\n- On-site via a camera\n- From the user’s phone gallery\n- From the user’s file system\n\nThis feature is supported for all attachment locations including: activity stream, functions, and input form screen.\n\n**Note:** This feature is also supported for scripted screens within Mobile App Bridge and the Cabrillo JS module.\n\n## Procedure\n\n1. Navigate to **All** > **System Mobile** > **Mobile App Builder**.\n\n The Mobile App Builder opens in a new browser tab and displays the application scope selection screen.\n\n2. Search for the application scope you are working in and then select the name of the application scope.\n\n The Mobile App Builder categories home screen displays.\n\n3. Select the attachment location for where you want to control the origin of the attachment source.\n\n\n
\n\nAttachment location\n\n\n\nProcedure\n\n
\n\n**Function**\n\n\n\n1. Select **Functions** from the menu and then select **New**. Alternatively, select an existing function record.\n2. Select **Upload attachment** in the **Type** field of the Properties section.\n3. Select **New** in the **Buttons attribute** section. The Button attribute record opens.\n4. Leave the **Button** field with the default name.\n5. Select **hidden\\_attachment\\_sources** from the **Name** field menu.\n6. Enter values in the **Value** field from where you don’t want images sourced from.\n\nValues can be `camera`, `files`, or `gallery`, or any combination separated by commas. If this field is empty, then images and files can be sourced from all locations.\n\n7. Select **Save**.\n\n\n
\n\n**Activity stream**\n\n\n\n1. Select the  **All mobile records** option from the menu.\n2. From the  **Record type**  field, select Activity stream screen \\[sys\\_sg\\_activity\\_stream\\_screen\\].\n3. Select **New** or an existing activity stream record. The activity stream screen opens.\n4. Select **Choose** in the Hidden attachment sources area.\n5. Select the attachment sources that you want to hide.\n6. Select **Apply**.\n7. Select **Save**.\n\n\n
\n\n**Input form screen**\n\n\n\n1. Select the  **Screens ** category, and then select  **New**.\n2. Select the  **Input form ** option in the Create a screen page, and then select  **Continue**.\n3. Select **New** in the Inputs section.\n4. Enter a **Name** and **Label** in the Properties section.\n5. Select `Attachment` from the **Input type** field in the **Settings** section.\n6. Select **New** in the Input attributes section. The Input record opens.\n7. Select **HiddenAttachmentSources** from the Name field.\n8. Select either camera, files, or gallery, from the **Value** field. The value you select is where you don’t want images sourced from.\n\n**Note:** To prevent images and files from more than one source, add additional **HiddenAttachmentSources** attributes after you save the attribute you're currently configuring.\n\n9. Leave the **Input** field value with its default entry.\n10. Select **Save**.\n\n\n
\n**Parent Topic:**[Working with images and attachments in mobile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/images-and-attachments.md)\n\n"}}