Work selectively with permissions

Illustrates different permissions in the proofing tool ProoferHive.

Invited - Paused - Reactivated

Many projects are created with all participants invited from the start. But some projects require stricter division as a certain person needs to act at the right time. If that’s the case, selective permissions can be helpful.

Projects where different roles are involved depending on the participant's task

A regular model where all participants are involved at the chosen time and remain all the way until the project is completed. The graph shows a timeline of the project’s start to finish, including time for archiving (dimmed color right).

1. Project start. The project is created by an agency or a marketing team (which uploads the the order, brief, script, etc.).

2. Creatives are invited.

3. Reviewers are invited and the feedback begins.

4. After final review/approval, the project is completed and can be published. Materials can be downloaded and delivered.

5. The project is archived.

Every time a person is invited (activated) to a project, they automatically receive an email notification with a link to the project. (presuming, however, that the person concerned has not enabled this basic default setting in their notification settings).

Projects where changes need to be determined before the creator acts

Here we have two ways of working. The first is presented here, and the new way can be accessed via the link below.

You can either open and close doors, like the model below, or work with personal notifications (@mention) to give a clear signal for various actions.



1. Project start. The project is created by an agency. (Who has received the order, brief, script via e-mail).

2. Creatives are invited and notified.

3. Coordinator is invited. During the review process, the creator is disconnected.

4. When the project manager and coordinator have agreed on what is de facto to be changed, then the creatives are reconnected and notified.

5. When the process is completed, a person is engaged to do the final approval.

6. After the final approval, the project is completed and can be published. Materials can be downloaded and delivered.

7. The project is archived.

N E W S !

There’s a feature that activates a "control person" where requested changes are reviewed by project managers etc. before they go on to the creatives. Read more about when requested changes need to be approved by a control person

 
Previous
Previous

If only I could sit next to you

Next
Next

WebP replaces jpg as the image display format in ProoferHive