Table of Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
Squirro's permissions model is based on Users, Projects and Roles. Users 'belong' to the particular Squirro Instance, so there's no need to create new Users for each Project. Administrators can assign Users to Projects, so that some Users may have access to some projects while others would not.
Viewing and editing project members
To view or edit project members,
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
Removing users from a Project
To remove a user from a project,
...
Removing a user from a Project does not delete the user from the Squirro instance – rather, it prevents the user from accessing a particular Project.
Permissions
Squirro's permissions model includes five roles: Server administrator, administrator, project owner, member and reader. Their relative permissions are as follows:
...
(any project)
...
(projects owned)
...
This page can now be found at Squirro Roles and Permissions on the Squirro Docs site.