====== Principles of RADIUSdesk Permanent Users ====== {{ :technical_discussions:permanentuserscreen.png |}} ===== Introduction ===== A Permanent User is typically connected to a warm body- \\ Someone you can call by name, most often a client who will pay you money for a service and hopefully make your business profitable. ===== Permanent User Similarities ===== There are certain similarities between Permanent Users as well as BYOD Devices and Vouchers. * They have a **Profile** associated with them. * They belong to a **Realm**. * They have an **Owner**. * Permanent Users and Vouchers both need a **password** to authenticate with. ===== Permanent User Specifics ===== These are the specifics that make a Permanent User a Permanent User. These items are not found in Vouchers. Some of these items may however also be found in BYOD Devices. * Permanent Users can have an **activation** and **expiry** date. This is a nice feature when contract workers will join your organization for a specified time period. You can register these users before they join and simply specify the date the account will become active and also when the account should expire. * A **hard** or **soft cap** for data or time can be added. If the profile associated with the user contains a data or time counter, you can **override** the cap type of this counter on a per user instance. * The **Personal info** of a Permanent User can be added. Since we want to build good relationships with our clients, we can record personal info on a user in order to meet the user's specific requirements in the future. * Assign **BYOD Devices** to users. In the emerging office where **BYOD** is becoming the rule rather than the exception, this feature makes it a snap to manage each user's devices. The BYOD principles will be discussed in a subsequent document. * Add **Notes** for each user. This can include comments like problems we may have experienced with a user or special arrangements we made with them. * Lastly, you can **pause or resume the recording** of the Permanent User's accounting for a time. This causes accounting records specific to this user to not be recorded in the program's database.