• As space administrator or confluence administrator, choose a space from the dashboard or just click on the globe icon next to the space in the dashboard and go to Browse Space -> Manage Users/Groups (tab)
• You can select a group here if there are groups that match space pattern defined in config that have viewspace permission.
  • If group actions are allowed in plugin config, you can: add a group, add a group and specify users, create multiple groups (enter a comma-delimited list of group names).
  • If you create a new group, the CSUM plugin gives the created group the "view" right to the space. You can manage permissions either by clicking on "edit space permissions" link at the bottom, or by going to space admin (tab) -> permissions. Select a group (create one first if there is not one already- don't worry- you can delete it) You can add users to groups by entering a comma-delimited list of usernames (ids). When a user is added to a group, one of the situations must apply:
    • The user must either exist according to Confluence (and Confluence may optionally in turn be using some other source like LDAP, Jira, Crowd, etc. for user management)
    • OR the user must exist in Jira (if plugin configured to use Jira's webservice for user management)
    • OR if the plugin is configured to use LDAP to gather user information for user creation, then:
      • If the user doesn't exist already in Confluence or Jira (depending on the "user manager" you choose in the plugin config) when you are adding a user to a group, it will lookup that user by username in LDAP, using Confluence's LDAP configuration supplied in atlassian-user.xml or osuser.xml. Notes: (1) The order of things in atlassian-user.xml and osuser.xml matter, as it will search for users in repositories in that order. If you don't want it to hit LDAP for users, but use the Confluence user tables instead, put the LDAP repository second in that config file. (2) Using LDAP for this plugin doesn't require you to be using LDAP for anything else in Confluence, but there's no problem if you are as long as you pay attention to point #1. (3) If you'd like the plugin to be able to use LDAP config from some other config other than atlassian-user.xml or osuser.xml or would like it to use some other source other than LDAP for user info for user creation, feel free to request an enhancement or better yet modify it yourself and see the contribution section about how to contribute that functionality, but please first look into whether Confluence can integrate with whatever authN/authR/SSO you would like it to use, since that is likely much easier.
      • It will then create that user in Confluence or Jira (depending on the "user manager" you choose in the plugin config)
      • It will then add that new user to the group specified.
  • You can remove users from the selected group by clicking on trash can.
  • If user search is allowed in plugin config, click on directory search link.
  • You can lookup users from entire userlist here and add/remove them from the selected group.
  • Click bulk actions link.
  • Here you can add/remove users from groups more quickly if you know the usernames (ids).

Here is some information that might help if you're trying to decide how to configure CSUM. Sorry if some of it is a repeat:

• The CSUM plugin doesn't care what you are using for user management, unless you are using Jira for user management (in which case, you should configure it to use Jira for user management). So feel free to use Crowd, LDAP, etc. The reason for this is that the CSUM plugin uses Confluence's own user API, which basically should (in theory) let the CSUM plugin use whatever Confluence uses for a repository.
• You don't need to configure the plugin for LDAP unless you want the CSUM plugin to automagically know about users that Confluence doesn't know about when you are trying to add those users to a group (or create a group with those users). If you configure CSUM to use LDAP for this purpose only when it can't find the users via the Confluence API, it will assume that you have an LDAP repository configured (and not commented-out) in atlassian-user.xml/osuser.xml. Note that if you do decide you want to use LDAP as a backup method of adding new users that don't already exist in Confluence when you add them to a group/create a group containing those users then be aware that Confluence itself will try to use the repositories in the order listed in atlassian-user.xml/osuser.xml. So if Confluence already has that LDAP repo listed, even if secondary, then why can't Confluence just see the users in LDAP? It's a good question, and the only answer I can provide at the moment is "don't ask". Maybe someone else can provide a better reason.
• Do not configure the plugin with LDAP configuration (using atlassian-user/osuser) if you don't have an LDAP repository setup in atlassian-user.xml/osuser.xml, because it won't work.
• There is no reason you have to use LDAP configuration in order to use CSUM, as long as Confluence already contains all of the users you would want to add to a group.