Feature Request

Considering the readers in the reader groups, the customer finds that they are arranged somewhat randomly, making it difficult to find a specific user, especially in the largest group, which has more than 200 readers. Customers could find readers more easily if readers were arranged alphabetically inside the reader's group.

Currently you can only add multiple categories when adding readers individually. On the import method you can only add one category. This means you now have to go into each imported reader and add the other category manually.

CURRENT ISSUE: When importing readers using the bulk import template, only the reader first name, last name, and email address can be specified. The "Content Access" and "Assign Groups" fields can only be completed after the bulk import and must be done individually for each reader. REQUEST: Add "Content Access" and "Assign Groups" columns to bulk import template to save time and make bulk user creation easier for admins.

Currently if you create a user and add it to a reader group they, by default, can still see everything in the project. you must manually on each reader user set documentation scope to NONE. this makes little sense. it would be nice to set a default documentation scope for all new users.

It is really useful for us to import Readers in bulk, since we have many! Therefore we are grateful for the excel import template. However, except for email, name and surname, we want to import (at least) two additional properties: 1)Reader Group(s) 2)"Document Scope" = "None" (write "yes" if applicable) This is because the individual Reader's permissions must be set lower than the Reader Group's permissions, otherwise the Reader Group's permissions will be overwritten by the individual Reader's permissions which, by default, is set to "Project". Currently, although we can import all Readers in bulk, we still need to go to each individual Reader to set the "Document Scope" to "None" in order for the Reader Group's Document Scope to apply.

When you are importing a large list of readers, in our example, 500 readers. They all have unique domains, we need the ability in the import file to specify the reader groups they are associated with.

current restriction of readers works on project/version/Categories. Would be usefule to have the capabilty also on individual articles or restrict by keyword/tag

Would be nice if the reader-export (CSV) feature (which is new and awesome :)) had other attributes beyond name and email. Ideally would have reader group membership, last login details and any other attributes easily passed to the CSV report.

While the Self-Registration works great, here is something that's required AFTER Readers have been allocated to one or more Reader Groups via self-registration: It would be extremely useful to be able to assign or remove Reader Groups to/from all readers with a particular domain name. Especially with a growing number of Readers. For example, if all existing Readers with domain example.org are assigned to Reader Group A (as arranged via Self-Registration), and they should now ALSO be assigned to Reader Group B, then it would be great to be able to do that at once, rather than going back to all of the individual Readers. As it works now, adding Reader Group B to the domain example.org would only affect newly signed-up users, however all existing ones remain linked to Reader Group A only. Hope this is clear - please let me know if more explanation of the issue and request is needed. Thanks for considering!

We would like to stage our user imports and then choose when to send out the invitation/verification. Right now when we import all of the readers are notified immediately. Providing the option to invite after import would be nice.