# BYOD & contractors ## The challenge Personal devices and contractor setups create a real access security problem. You need to ensure only the right people can access company resources from the right devices — but you cannot enroll personal devices into corporate MDM, you cannot issue hardware to every contractor, and traditional onboarding processes are too slow for short engagements. At the same time, simply handing out credentials is not an option. Passwords get shared, phished, and forgotten. And when a contractor's engagement ends, there is no reliable way to know that all their access has been revoked. *** ## How Peig solves this Peig gives you control at both the identity and device level — without requiring MDM or corporate hardware. Every device that accesses your workspace must be explicitly registered and approved. You decide which devices get access, and you can revoke access from a specific device at any time — independently of the user's account or their other devices. This means: * **Device-level control without MDM** — you do not manage the device, but you control whether it can access your workspace * **Per-device authorisation** — each device is individually registered, approved, and can be individually suspended or removed * **Scoped access** — each user only sees and can access the services they have been explicitly granted * **Instant revocation** — suspending a user or a specific device blocks access immediately, across all services *** ## Setting up access for a contractor 1. Create a user account for the contractor in **Users & Access** 2. Assign access only to the specific services they need — nothing more 3. For SAML applications, set a Provider ID for each service 4. Send them an invitation to download Peig and join the workspace 5. The contractor registers their personal device — you approve the request and their device is authorised When the engagement ends, suspend their account. Access is revoked immediately across all services and all their devices. {% hint style="warning" %} For SAML applications, remember to also manually remove the contractor's account in the application itself after suspending them in Peig. See [Offboarding](file:///3832028/admin-guide/offboarding.md) for details. {% endhint %} *** ## Setting up access for BYOD employees The process is identical to any other user onboarding — employees download Peig on their personal device, join the workspace, and their request is approved by the Access Admin. The device is registered and authorised without any management software being installed on it. Employees can register multiple devices — a personal laptop and a phone, for example. Each device is managed independently. If a device is lost or should no longer have access, it can be suspended or removed without affecting the user's other devices or their account. *** ## What this looks like in practice * A new contractor starts on a Monday. By Monday morning their account is created, access is scoped to the two tools they need, and their personal laptop is registered and approved in Peig * Three months later the engagement ends. One click suspends their account — access to every connected service is revoked immediately from every device * An employee loses their personal laptop. The device is suspended in Peig immediately — their phone and other registered devices are unaffected and continue to work normally --- # Agent Instructions: 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: ``` GET https://docs.peig.io/welcome-to-peig-documentation/use-cases/byod-and-contractors.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.