Access Privileges in MaxWhere
As a MaxWhere user, your access privileges in terms of the spaces you can open and whether or not you can add / edit 2D content will vary from space to space and from project to project. On this page, you will find a brief explanation of the different access levels that are defined in terms of access to spaces and projects.
Access levels for spaces
In general, each user can have one of five access levels to any given space in MaxWhere:
- No explicit access: This is the default case. If a user has no explicit access to a space, he or she can only view the space if its visibility has been set to public (see further below)
- Viewer access: The viewers of a space can open the space, whether in the MaxWhere Desktop Client or on MaxWhere Web, even if the visibility of the space has been set to private (see further below)
- Editor access: The editors of a space can open the space, in just the same way as viewers can. In addition, editors can create any number of 2D projects within the space, using the Editor Menu available in the MaxWhere Desktop Client.
- Administrator access: The administrators of a space can do everything that the space editors can do; in addition, they are granted privileges to modify the metadata of the space on the MaxWhere Portal, and to modify the sharing options of the space (i.e., grant access privileges to other users)
- Owner access: The user who created the space is the single owner of the space. The owner of a given space can do everything that its administrators can do. In addition, the owner can grant administrator access to any MaxWhere user.
Visibility of spaces
All spaces in MaxWhere have an associated visibility, which can be either public or private. In addition, any given space can optionally be configured as unlisted.
Spaces that are public can be opened by any MaxWhere user. Spaces that are private can only be opened by users who have explicit privileges to either view or edit them. Spaces that are unlisted do not appear to their potential viewers in the Space Browser (not even through the search bar); however, they can be accessed via their own unique sharing link, which can be accessed by the creator or administrators of the space via the MaxWhere Portal. Note that even in case a space is unlisted, it will nevertheless appear on the MaxWhere Portal to its administrators and owner (otherwise, they would be unable to modify the settings of the space).
Access levels for projects
In a way similar to the spaces, users can also have access levels with respect to individual projects inside the spaces, as follows:
- No explicit access: A user who does not have any explicit access to a project can see and open the project only if its visibility has been set to public. If a project is private, the user will not even see it listed anywhere (not on the Project Explorer, nor on any Selection Panel).
- Viewer access: A user who has viewer access to a project can view the contents of the project, even if its visibility has been set to private (note that a prerequisite to this is that the user has the privileges to open the space to which the project belongs in the first place).
- Editor access: A user who has editor access to a project can change the content loaded into its smartboards, change the properties of its smartboards, as well as add and remove smartboards to and from the project.
- Owner access: The user who created the project is the single owner of the project. Owners can do everything that project editors can do. In addition, they can grant editor and viewer access to the project for other MaxWhere users.
Visibility of projects
In much the same way as with spaces, project visibility can be set to public or private. In addition, projects can optionally be set to unlisted. In this case, the given project will not appear on any user interface inside the space. Still, this can be a useful setting if the project is also set to autoload. In this case, the project will be loaded automatically by MaxWhere when the space is opened. Also, projects that are unlisted still show up to their owner and editors (otherwise there would be no way to modify their properties). Thus, setting a project to unlisted can also be a way of making sure that the general public cannot see it for the time being (even if the project is public).