Hey Kirc. Thanks for the feedback.
"Team Members have ability to create, edit or modify, but no access to the Portal View."
The Team Member role does have Portal access:
I think you may have read the User Role documentation to mean that anyone that is not a Consumer does not have Portal access. We have refined the document to avoid such confusion:
Update from user:
Okay, I must have been misled by my user(s), I did a guineapig user who was not imported, so I can set her role to whatever I needed to test.
As Team Member, she has Portal Access.
Now to pass her into workflows for low level distribution development…. Will get back to you on those results, if they satisfy the need.
Thanks for the update. We are happy to see users leveraging the InfoBurst Portal. The use case you propose we have not seen before (Workflow user + Portal). Currently, A Workflow-only user does not currently see a Portal option in the main user interface. We will be adding this option in 2023.2.
Please disregard my last reply. After consideration, we have decided not to add a Portal option for a Workflow-only users in the main user interface. This is because Portal is not a delivery destination for any Workflow.
Kirc Breden
Currently, the Consumer Role has Portal View access, but no access to create, edit or modify.
Team Members have ability to create, edit or modify, but no access to the Portal View.
I propose a new Role to come between the Team Member and Project Manager, with a bit of both plus Portal View Access to allow them to see the fruits of their labor while creating solutions for distribution.
Current:
User Roles
Role
Access Rights
Administrator
System Operator
Project Manager
Team Member
Consumer
Recipient
Proposed:
User Roles
Role
Access Rights
Administrator
System Operator
Project Manager
Developer
Team Member
Consumer
Recipient