TeamForge EventQ is authenticated and authorized by TeamForge, using TeamForge
users, permissions and roles. To access TeamForge EventQ features, TeamForge users need
additional permissions on a project by project basis.
TeamForge EventQ requires a valid TeamForge user session for access. If you try
to access TeamForge EventQ when you are not logged in or when your session has
expired, you will be directed to the TeamForge login page. After you successfully
log in, you will be automatically redirected to the target TeamForge EventQ
screen.
Permissions
TeamForge EventQ permissions are set in the "Project Admin" area on a project by
project basis. The following EventQ permissions may be used in creating TeamForge roles:
- EventQ READ —
The
minimum required permission users need to view EventQ based data such as the
Activity Stream and EventQ-based associations.
- EventQ EDIT —
Required
to modify EventQ data sources via the interface. Users with the "EventQ EDIT" permission are
implicitly granted the "EventQ READ" permission.
- EventQ CREATE —
Required
to create new EventQ data sources via the interface. Users with the "EventQ CREATE" permission are
implicitly granted the "EventQ READ" and "EventQ EDIT"
permissions.
- EventQ API —
Required
for read and write access to EventQ HTTP APIs such as the Source API and the
XDS schema API. TeamForge Site Administrators do not explicitly require this
permission; however, all other project members, including Project
Administrators, require this permission to use the EventQ HTTP
API.
- REPORTING API —
Required
to retrieve data from the EventQ Reporting API.
Note: TeamForge EventQ does not immediately reflect permission changes.
Permissions are automatically refreshed daily. To reflect permission changes
more quickly, log out of TeamForge, wait 10 minutes, and then log back in
again.