How can one use the permissions system in FogBugz to restrict users' access?
|
6
4
|
|
|||
|
|
|
5
|
As of FogBugz 8, FogBugz allows you to set up groups of users who can be granted permissions to read or modify certain parts of FogBugz selectively. FogBugz users can be given permission directly on Projects, Wikis, and Discussion Groups, or they can get permission through a group. Setting Up Permissions Before setting up permissions, ensure that FogBugz is configured to require passwords (Admin | Site | Authentication | Log on Method). Groups Groups in FogBugz are lists of users that can be given permission on Projects, Wikis, and Discussion Groups. Before you setup permissions in FogBugz, you may want to organize your users into groups. In addition to any groups you create, there are 4 automatic groups on every FogBugz install that are considered when assigning permissions:
These groups let you easily give all users access to a project, wiki, or discussion group. For more information, see this article. Projects Access to cases is controlled at the project level. Normal users can be given permission to view cases, submit cases, or to be a project administrator. Community users can only be given permission to submit cases and view cases they have already submitted. To setup project permissions:
Wikis and discussion groups Both normal and community users can be given access to a Wiki or Discussion Group. Normal users can be given read, write, or administration privileges, while community users can be given permission to read or write only. To setup wiki or discussion group permissions:
Administrators There are two types of administrators: Site Administrators, and administrators who have been given permission on a specific Project, Wiki, or Discussion Group. Site administrators are a special type of FogBugz user designated in Admin | Users. They have full control over all areas of FogBugz, and are the only users that can edit permissions or Create/Delete Projects, Wikis, and Discussion Groups. Non-Site Administrators get control over their respective areas, described below: Projects Project Administrators can't create or delete projects, or assign project admin permissions to other users, but otherwise have full control over their own projects, including the ability to:
Wikis Wiki administrators can't create or delete wikis, or assign wiki admin permissions to other users, but otherwise have full control over their own wikis, including the ability to:
Discussion groups Discussion Group Administrators can't create or delete discussion groups, or assign discussion group admin permissions to other users, but otherwise have full control over their own discussion groups, including the ability to:
Isolating users from one another In various parts of the FogBugz user interface, you can see a list of users in a dropdown list. FogBugz will only show each user the names of people who have some project or group in common. For example, Alice and Bob will not see each other's names in any dropdown lists with the following group setup:
However, suppose we create a Project called Bob's Project and give the Development Group and Bob permission on it. Then Bob and Alice would be able to see each other. Also note that if we give All Normal Users permission on a project than everyone can see everyone in a FogBugz install. Mailbox Usage Rules In order for a user to send mail from a specific mailbox, they must have Modify access to a project and the mailbox they wish to use must be set to sort incoming messages into an area in that project. Only if these conditions are met will a user be able to send outgoing mail from a given mailbox. Other Visibility Rules There are a few other rules to keep in mind if you are concerned about user visibility in your FogBugz install:
Our QA Process Regarding Permissions We test to make sure permissions work with every single release that we do. The basic workflow that we walk through is:
|
|||
|
|
