Assigning Permissions

Now that you know the theory of assigning permissions in FogBugz, it's time to look at how it works in practice. FogBugz supports three levels of permissions:

• None: A given user does not have permission to see or modify cases.

• Read: A given user can read cases, but can't modify them in any way.

• Modify: A given user can read and modify cases.

Permissions are set up on a client or department basis, and then applied to all projects assigned to that client or department. When you are editing a client or department in FogBugz, you have three choices. First, you can choose to give everyone full access to the client or department, as shown in Figure 3-12. This is the default. With this setting, you can't change the permissions for individual users.

All users can read and write cases associated with this client. All users can read cases associated with this client. Customize:

I None Read

Modify

User I

(Admin)

Administrator

r r

?

Ben Womack

r r

Herbert Rasmussen

r r

Jeff Ohura

r r

Karen Benson

(Admin)

Mike Gunderloy

r r

Paige Nagel

r r

Randy Wilson

r r

Robert Evers

r r

Terry Eagan

(Admin) (* Valerie Shrlver All administrators can read and write cases associated with any client.

(Admin) (* Valerie Shrlver All administrators can read and write cases associated with any client.

Figure 3-12. Giving everyone full access to a client

The second choice is to give everyone read access to the client or department, as shown in Figure 3-13. In this case, you can control on a user-by-user basis which users can modify cases for the client or department. Administrators, though, will always have modify access.

and write cases associated with this client, cases associated with this client.

All users can read All users can read Customize:

None Read

Modify

User

(Admin)

Administrator

r r

(•

Ben Womack

r r

(•

Herbert Rasmussen

MH^il

r

Jeff Ohura

r r

(*

Karen Benson

(Admin)

(*

Mike Gunderloy

• 0

r

Paige Nagel

r e

r

Randy Wilson

r r

Robert Evers

r r

f*

Terry Eagan

(Admin)

f*

Valerie Shriver

All administrators can read and write cases associated with any client.

All administrators can read and write cases associated with any client.

Figure 3-13. Giving everyone read access to a client

Permissions: f, a c

All users can read All users can read Customize:

Finally, you can choose to customize access to the client or department. In this case, you can choose on a user-by-user basis whether to assign none, read, or modify access. Administrators still get modify access automatically, as shown in Figure 3-14.

and write cases associated with this client, cases associated with this client.

All users can read All users can read Customize:

I None Read

Modify

User I

(Admin)

f*

Administrator

(* r

r

Ben Womack

r r

(*

Herbert Rasmussen

r (*

r

Jeff Ohura

(* r

r

Karen Benson

(Admin)

f*

Mike Gunderloy

r 0

r

Paige Nagel

r 0

r

Randy Wilson

r r

f*

Robert Evers

(* r

r

Terry Eagan

(Admin) (* Valerie Shriver All administrators can read and write cases associated with any client.

(Admin) (* Valerie Shriver All administrators can read and write cases associated with any client.

Permissions: f, c a

All users can read All users can read Customize:

Figure 3-14. Assigning custom permissions for a client

It's important to understand the consequences of your choices in editing this section of clients and departments. If you choose option #1 or #2 for any client or department, you will not be able to completely segregate groups of users from each other, because they can meet each other in that client or department. The net effect is that if you want to use permissions to keep users separated and hidden from one another, you need to set up custom permissions for every single client and department.

■Caution Don't forget to set custom permissions on the default Internal client when you're setting up a custom permissions scheme.

Anyone who is configured as a FogBugz administrator will always have permission to read, write, and modify any case, anywhere. A corollary of this is that the administrators can see all of the other users, and all users can see the administrators.

To sum up, there are four things you need to do when setting up a custom permissions scheme in FogBugz:

• Use the Site Options screen to ensure that FogBugz is configured to require passwords to log on.

• Create the appropriate clients or departments.

• Edit the clients or departments to assign user permissions appropriately.

• Assign each project to the appropriate client or department.

0 0

Post a comment