Date: Fri, 29 Mar 2024 00:02:05 +0100 (CET) Message-ID: <1789853993.6134.1711666925066@k5115.pixsoftware.de> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6133_480633440.1711666925066" ------=_Part_6133_480633440.1711666925066 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The LANCOM Management Cloud has a roles- and rights system. This allows = users with different rights to operate the LANCOM Management Cloud. The dif= ferent user roles and rights are explained in this document. They are based= on the organizational and project level.
The organization administrator can create= several projects for his organization and manage the organization.
Once he has created a project, he is assi= gned the role of a project administrator in it. The organization administra= tor is usually an employee of the LANCOM partner.
The organisation observer has no administ= rative rights, only read access to organisation information. They can see a= ll projects and devices as well as properties of the organisation. Other us= ers of the organisation and the log view cannot be viewed.
The organisation observer is usually an e= mployee of the LANCOM partner who is to be given administrative access to t= he organisation's projects via user inheritance.
The project administrator has all rights = within the corresponding project.
A project administrator is usually an emp= loyee of the partner, but it is also conceivable that an employee of the en= d customer works as project administrator.
The technical administrator can
Unlike the project administrator, however= , the technical administrator does not have the authority to manage or invi= te new project users and cannot modify project information and project prop= erties. The role of technical administrator is usually assigned to an emplo= yee of the end client.
The project member can
This user role cannot modify project info= rmation and project properties and has no access to log data. The project m= ember is usually a support staff member of a larger partner, who is respons= ible for a quick resolution at the customer's site.
Users who have been assigned the = role of rollout assistant can use the LMC rollout app=
While the Rollout Assistant role can also= create and modify user-specific dashboard content for its own user account= , the role was not actually designed to operate the LMC configuration inter= face. It has been created exclusively to be used in the LMC rollout= app and communicates only with the APIs of the LMC.
The hotspot operator role has exclusive a= ccess to the hotspot portal within the LANCOM Management Cloud.
In the hotspot portal, the hotspot operat= or can create and download vouchers for the projects assigned to him as wel= l as customize user-specific contents of his own user account.
The project observer does not have any ad= ministrative rights but has read-only access to device and project defaults= . Device and project logs cannot be viewed either.
However, he is able to create and modify = user-specific dashboard content for his own user account.