Skip to main content

User roles

Availability-noteDeprecated

Referring to the stages to build an analytical document, users of Talend DQ Portal platform can have a specific function assigned by the administrator.

Users can be classified into 4 different groups:

  • Administrator: deals with configuration and security aspects,

  • Developer: creates or modifies document templates,

  • Tester: verifies the formal correctness of the registered document templates and if they fulfil the requirements.

  • End-User: uses all the developed document templates in a Released state, according to his/her role and with the modalities previously defined in the parameters configuration by the BI administrator.

Information noteNote: Administrators, developers and testers are also users and, therefore, they can act as specialized users with additional functions.
Information noteNote: Talend DQ Portal groups the administrator, developer and tester roles under one unique role: BI administrator. When you access the Portal as an administrator, you can: create document templates, test the document templates, validate the tested document templates to make them available for the end-user and finally manage the end-user page and security aspects. However, as a BI administrator, you can assign the specific rights to access Talend DQ Portal as a pure developer or tester.

After developing the document template, you must update its state to Test. You can then test the document template, and depending on the test results, you can change the document state back to Development or to Released. When the document template is in the Released state, the end-user can use it in the end-user page of Talend DQ Portal. For detailed information on managing document templates, see Document management.

For more information, download the SpagoBI quick start guide from SpagoBI Documentation at http://forge.objectweb.org/project/showfiles.php?group_id=204 or check http://wiki.spagobi.org/xwiki/bin/view/spagobi_server/.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here