<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Licensing on ProRDP - RDP to your Mac</title><link>https://prordp.app/docs/licensing/</link><description>Recent content in Licensing on ProRDP - RDP to your Mac</description><generator>Hugo</generator><language>en-US</language><atom:link href="https://prordp.app/docs/licensing/index.xml" rel="self" type="application/rss+xml"/><item><title>Licensing a Mac</title><link>https://prordp.app/docs/licensing/mac/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://prordp.app/docs/licensing/mac/</guid><description>&lt;p&gt;This guide takes you from nothing to a licensed Mac. It covers the one-at-a-time route, where you&#10;approve a short code shown on the Mac. To license many Macs without visiting each one, use&#10;&lt;a href="https://prordp.app/docs/licensing/mdm/"&gt;MDM enrollment&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>MDM enrollment</title><link>https://prordp.app/docs/licensing/mdm/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://prordp.app/docs/licensing/mdm/</guid><description>&lt;p&gt;Activating Macs one at a time, with a code, doesn&amp;rsquo;t scale. With &lt;strong&gt;MDM enrollment&lt;/strong&gt;, you create an&#10;&lt;strong&gt;enrollment key&lt;/strong&gt; in the portal and push it to your Macs as a setting. Each Mac licenses itself the&#10;next time ProRDP launches, with no prompt and no one signing in.&lt;/p&gt;</description></item><item><title>Roles and members</title><link>https://prordp.app/docs/licensing/roles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://prordp.app/docs/licensing/roles/</guid><description>&lt;p&gt;A workspace&amp;rsquo;s &lt;strong&gt;owner&lt;/strong&gt; can give other people in their organization access to it. Each person is&#10;given one of three &lt;strong&gt;roles&lt;/strong&gt;, which decide what they can see and do. This page covers the roles, how&#10;to add members, the rules that keep a workspace from being locked, and how scripts and pipelines&#10;use the same roles through the workspace API.&lt;/p&gt;</description></item></channel></rss>