User roles for Publishing Document Builder

Review the list of user roles and the permissions that come with each role for Publishing Document Builder.

Table 1. Publishing Document Builder user roles
Capabilities	Report designer (`pub_report_designer`)	User (`pub_user`)
Access the Administer menu option	N/A	N/A
Monitor system health, view all running jobs, and assign runtime and environment variables.	N/A	N/A
Upload templates and style sheets into the Publishing Document Builder		N/A
Assemble reports (in Reports tab)		N/A
Define data source connections.		N/A
View output files and logs about their document-style report generation jobs
Schedule document-style report generation
Generate document-style report from the Publishing Document Builder
Mark reports as available or unavailable to other users		N/A

Resources permissions

On the Resources tab, resources can be shared between designers by setting their ownership and privacy for individual resources and reports (templates, style sheets, scripts, and reports). Users can also add owners for these resources. If you are an owner of a resource, you can edit the resource. You can set permissions for a resource by clicking the Ownership & permissions icon in the edit column for individual resources on the Resources tab.

Administrators have access and rights over all resources, regardless of their privacy and ownership settings. Report designers can access all the resources that they created and all public resources. A resource can be either public or private.

Public resources are visible to all designers and can be used to create reports. Public reports can be used by users to generate document-style reports. Public resources can only be edited by either their creator, administrators, or other owners (report designers) that were added as owners to the resources by using the Permissions window. Connections are treated as common resources and are public. Although connections are public, credentials are not. Every user that is generating a document-style report must enter their own credentials for a connection during document-style report generation.

Private resources are editable by and visible only to their creator, administrators, or other owners.

Table 2. Publishing Document Builder report visibility and ownership according to role
Report visibility and ownership	Administrator	Report designer
Private / Mine	Can edit and view.	Can edit and view.
Private / Others	Can edit and view.	Not visible
Public / Mine	Can edit and view.	Can edit and view.
Public / Others	Can edit and view.	Visible but cannot edit.

Private resources are editable by and visible only to their creator, administrators, or other owners.

Table 3. Publishing Document Builder report visibility and ownership according to role
Report visibility and ownership	Administrator	Report designer
Private / Mine	Can edit and view.	Can edit and view.
Private / Others	Can edit and view.	Not visible
Public / Mine	Can edit and view.	Can edit and view.
Public / Others	Can edit and view.	Visible but cannot edit.

Mapping PUB roles to JTS roles

If you have delegated authentication for Publishing Document Builder to a Jazz® Team Server using either container or SSO authentication, the roles for Jazz Team Server users can be mapped automatically to Publishing Document Builder, eliminating the need for administrators to manually add users as admins or report designers. Administrators can change the mapping for the default roles, add, or delete new roles.

Table 4. Default mapping of Publishing Document Builder roles to Jazz Team Server roles
Jazz Team Server role	Publishing Document Builder role
JazzAdmins	Administrator (pub_admin)
JazzProjectAdmins	Administrator (pub_admin)
JazzUsers	Report Designer (pub_report_designer)
JazzGuests	End user (pub_user)