----- ====== Principles of RADIUSdesk Profiles ====== ===== Introduction ===== A profile is assigned to each voucher, permanent user and BYOD device. Profiles are used to control the behavior of the RADIUS client through which a user (voucher, permanent user or BYOD device) connects to the network. This includes the following points: * Limiting the bandwidth. * Limiting the total data available over a certain period of time, e.g. a monthly data cap. * Preventing the user from connecting before a certain date. * Preventing the user from connecting after a certain date. ===== Profiles and Profile Components ===== * Each profile can consist of zero or more profile components. * Profile components can be considered as small functional blocks or groups * For example, you can have a profile component that limits the bandwidth of a user's connection. ===== Simple Edit ===== * The Profile applet contains a simplified editing interface where you can select which restrictions you want to make in the profile. * When you save it, the system creates the profile with its profile components based on the elements selected in the simplified editing interface. ===== FUP Edit ===== * The Profile applet also contains an interface for editing Fair Usage Policies (FUP) * This should be used if you want to implement Fair Usage Policies. * The FUP functionality is covered on a separate page for advanced users. ===== Advanced Edit ===== * The advanced editing option allows you to manually add or remove profile components from a profile. ===== Clouds and Profiles ===== * A profile is usually part of a cloud (owned by a cloud). * However, it is possible to make a profile system-wide. ===== System Wide check ===== * If you have logged in to RADIUSdesk as the root user, there is a System-wide checkbox that you can activate. * If you activate it, the profile becomes available in all clouds.