New feature discussion: Assignments

Hey all,

Just wanted to get a conversation going around the new assignment feature we shipped last week. You’ll notice now when you launch a process and open the “Menu” pane in the upper right, you’ll see there’s an “access” section. This section displays everyone who has access to the process.

Initially, everyone will show up as “Not assigned”. If no one is assigned, everyone with access to the template will show as responsible for that process in the dashboard. If designate someone as “assigned,” then only that person/people will show as responsible.

Feel free to play around and let us you if you have any thoughts / comments.


Hey this looks great! Questions:

  • How will this affect Review steps? Are people granted access able to provide that review? Conversely, if I add someone, can I restrict them from being able to review?

Thank you!

@jack.moreau Review steps are independent. If you add someone as a reviewer on a template, they’ll automatically be added as a global member of that template, and will have access to every one of its processes (this is the same behavior we’ve always had, no changes). When landing on a review step, the system will still determine the review responsibility to be the person indicated in the template (again, no changes here). The only things that change with this new feature are:

  1. You can now give someone access to a single process, without having to give them access to every process of that type. This also helps keep that person’s dashboard unpolluted.

  2. Before we made this change, if there was no specific person responsible for an action (eg. payment, review), then the dashboard would show that everyone who had access to the template was responsible. Now, this will only be the behavior if no one is assigned. If someone is assigned, it’ll just be the assigned people’s responsibility, which again, should cut down on the noise happening in everyone else’s dashboard.

Note, if you want to guarantee that someone will always be assigned, you can use the assign someone step. That way the responsibility will always be sent intentionally to a specific person rather than the group.