- Security & Authentication
- System & Performance
- Profiles - Datasources - Filters - Lists
- Users - Collections - Service Accounts
- Data Processing
- Release Notes
Collection Managers are the "superusers" for Angelfish. A successful Angelfish implementation generally has at least one Collection Manager for each Collection.
Collection Managers have admin capabilities (create, edit, delete) for Objects in a Collection. These Objects include:
Collection Managers can use Service Accounts in Datasources and Lists, but have no admin capabilities for Service Accounts.
Collection Managers also receive AYA (Ask Your Admin) questions for the Collections they manage.
WHY ARE COLLECTION MANAGERS NEEDED?
With Angelfish, the end users who view the reports often have a different perspective from the admins who manage the config settings for the reports.
The Collection Manager status gives end users the ability to fix bad data in the Profiles they use, without needing to be an admin for the entire application.
HOW TO CREATE A COLLECTION MANAGER
Global Admins can assign Collection Manager status to Standard Users. Collection Managers are assigned in the config settings (Collection Managers tab) for each Collection, in Global - Collections.
Global Admins are able to configure settings for all Objects and view reports for all Profiles, and do not need to be assigned Collection Manager status.
If you'd like to become a Collection Manager, you first need to learn how Angelfish works.
We recommend starting with these resources: