User Types in FogBugz



This article provides information about the different types of Users in FogBugz.

Please read more about Managing Users and how the  Permissions and Visibility are applied.


In FogBugz, there are five types of users, based on access rights:



  • The Administrator role type has the highest level of user permissions.
  • There must be at least one Administrator user on a FogBugz account at any given time.
  • Any user can be promoted by one of the existing Administrators, to become an Administrator themselves.
  • An Administrator can also demote any other Administrator to one of the other user types (but they cannot demote themselves).

An administrator has permission to do anything in FogBugz:

  • Access the Admin menu and Admin Dashboard;
  • Configure and add users, and change their passwords;
  • Set up projects, areas, shared filters and snippets, and groups;
  • Create new planners and milestones;
  • Configure all site settings and site working schedule;
  • Customize each project's workflow.

In addition to the above, FogBugz Site-Administrators can designate any user as an administrator over a project. See Permissions. 


Back to the top

Normal Users

A normal FogBugz user. Normal users have access to cases, wikis, discussion groups, and reports as determined by permissions. 


Back to the top

Virtual Users

A virtual user cannot log on and does not use up a license. Its purpose is to allow assigning of cases to a group of people instead of an individual. For example, you could create an "Up For Grabs" virtual user that serves as a sort of work queue and owns a case until someone assigns it to themselves. Link to it all the email addresses (comma separated) of the users you want to be notified when a case is assigned to create a notification list. To enable email notifications from this user, provide the desired email address(es) and notification preferences.


Virtual Users for Integrations

Integrations like GitHub can cause "new users" to appear in the user list as "(imported)" accounts.

For example, when users commit to configured GitHub repositories, we check to see if any FogBugz users exist with the same Full Name or Email Address. If not, we create a new Virtual User for that GitHub committer. 


These imported users do not require a license and can be safely deactivated.



Back to the top

Community Users

These users are allowed to partially (e.g., limited access) open up FogBugz to the outside.

  • Community users can log on to FogBugz and require email verification. 
    Once logged on, they:
    • can see a list of their cases including case number, case title, status, and date opened;
    • can click into each case to view the entire email communication trail (they cannot see internal edits); 
    • can also view the ticket URL and ticket ID.
  • Community users can be an individual, or part of a group, to submit cases on a project-by-project basis. This is not very different from submitting cases via email.
  • Community users must be enabled or disabled (functionality). 
  • Community users receive only an auto-reply email and explicit email replies from you, and not any other notifications.
  • Community users can see a list of all cases in specified projects if the Community Case List feature is enabled.

When Community users are added to groups,  you can restrict the visibility of a wiki to a subset of users. Only wikis and discussion groups can be fully opened to community users through a community wiki.


Back to the top

Anonymous Users

If you would like to open wikis, discussion groups, or the creation of cases up to the public at large, then you can choose to give access to anonymous users.

For wikis and discussion groups, these users can read and edit depending on the permissions you have configured.

When an anonymous user opens a case, you will see the first event on the case stating "case posted to the website."

Back to the top