> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/administration/settings-center/compliance-and-security.md). # Compliance & Security Use this section to control how tracking behaves across your organization: block restricted websites, set organization-wide privacy safeguards, restrict where the app can be used, tune the desktop agent, and review a record of administrative actions. For an overview of what these controls mean, see the [Compliance & Security reference](https://docs.we360.ai/reference/work-and-time-management/user-interfaces/portal/settings-center/compliance-security). {% hint style="info" %} These settings require **Super Admin** access, apply organization-wide, and can take up to an hour to reach every device. {% endhint %} The tab is organized into six areas: **Domain Blocking**, **Compliance**, **Location Restriction**, **Stealth App Config**, **Standard App Config**, and **Audit Logs Report**. ## Domain Blocking {% hint style="info" %} Domain Blocking is currently in **Beta**. {% endhint %} Create named groups of websites to block, then apply them to specific teams. For each group you set: * **Category name**: a label for the group of domains. * **Domains to block**: choose from known applications and websites, or add your own. * **Teams**: the teams the block applies to. * **Blocking method**: * **Default**: standard-app users see a warning; stealth-app users are blocked automatically. * **Force Close**: the browser closes shortly after a restricted site is opened, for both user types. Existing groups appear in a searchable table showing the blocked domains, the teams affected, the blocking method, and when each group was last updated. ## Compliance Organization-wide privacy and data-protection controls: | Setting | What it does | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | **Screenshots Capture** | Turns screenshot capture on or off for the whole organization. | | **Screenshots Download** | When off, screenshots can't be downloaded from the portal. | | **Screenshot encryption** | Adds end-to-end encryption for screenshots. Contact support to enable it. | | **Screen Recording** | Turns session recording on or off. Requires desktop app version 4.8.12 or later. | | **Allow support access** | Lets the We360.ai support team access your account to help with configuration. Revoke it any time. | | **Set screenshot blur** | Opens a slider to blur captured screenshots, protecting on-screen detail while keeping activity visible. | | **USB Detection** | Logs when external USB devices are connected or removed, supporting data-loss prevention. | | **Handle Tracking Anomalies** | Enables automatic correction or flagging of tracking anomalies. When on, **Configure Anomalies** lets you define the rules to apply. | ## Location Restriction Control where employees can punch in, access the portal, and be tracked, based on your saved office locations. You can create up to five **Allow** rules and five **Deny** rules. Each rule targets one or more teams (or all teams) and applies to any combination of: * **Punch In/Out** * **Portal Access** * **Device Tracking** Changes apply across the organization and can take a couple of hours to take effect. ## Stealth App Config Fine-tune how the silent (stealth) agent creates and manages user records: * **Auto manage users**: automatically activate or deactivate stealth users based on the activity received. * **Skip system root user**: don't create a stealth user for the system root account. * **Use email prefix as employee ID** and **Use hostname as last name**: control how new stealth users are named. * **Mark new stealth users as non-tracking**: create new stealth users without tracking until you turn it on for them. * **Skip user creation for specific usernames**: exclude system or service accounts (usernames are case-sensitive). An advanced section controls how stealth-user email addresses are generated. {% hint style="warning" %} Changing the email prefix or suffix can affect existing devices and may cause new user records to be created. {% endhint %} ## Standard App Config Control how the visible (standard) desktop app behaves: * **Enforce Internet Access**: require an active connection to punch out or end a break. * **Allow Login Without Browser**: let employees sign in without a web browser, or require browser-based login. * **Always On Mode**: keep tracking outside punch-in hours, or track only while punched in. * **Auto Punch-In Mode**: set the app's automatic punch-in behavior. You can turn it off, or have users punched in the first time the app opens each day, whenever the app is running, or during their assigned shift. ## Audit Logs Report {% hint style="info" %} Audit Logs is currently in **Beta**. {% endhint %} Review a record of administrative actions taken in the portal (changing a rule, editing a timesheet, or removing a user), each stamped with the time and the person who made the change. Filter by date range and user, then download the results as a CSV. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.we360.ai/administration/settings-center/compliance-and-security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.