CityGrows supports the following role types with associated permissions and access levels:

Applicants (constituents and businesses): This is the role type for anyone from the public who is applying for a permit, process, or license. Applicants access CityGrows via pages on the https://go.citygro.ws domain (you'll notice that all applicant pages start with "go." During account setup, applicants submit their name, email and password, and if they log in to https://go.citygro.ws are able to see all the processes they've launched on the CityGrows system. Applicants can access detailed data about their own processes, and can see aggregate data through CityGrows Stats pages for any public process.

Government account roles:

You can see all of the people who have administrative access to a workflow from the Edit screens/  Permissions tab.

Owner: The person who creates a new workflow on CityGrows is the workflow Owner. The Owner can add and remove other Admins, but the ownership of a workflow can't be transferred. An owner can edit all aspects of a workflow.

Admins (Edit workflow": Admins are the CityGrows users who can edit, use and manage workflows on the CityGrows platform. Anyone who joins CityGrows via the https://citygro.ws/users/sign_up page is able to set up and manage their own workflows. If create a workflow, you're an Owner and an Admin, but many people can have Admin privileges on the same workflow. Unlike many other software companies, we don't put any limit on the number of admin users a government can have use our system. We want to encourage more people in your organization to use technology, not fewer!  Admins can also add Reviewers and create Teams (see below). Usually, one or two Admins in each department or government become CityGrows "power users" and act as a resource for other staff. 

Admin (Use workflow): Sometimes you want people on your staff to be able to use and review on a workflow, but you don't want them to be able to edit the questions, steps or other information for that workflow. In that case, select "Use workflow" for those people if you add them as admins under the Permission tab.

Reviewers: Reviewers are CityGrows users who have been invited to a workflow to review applications. When an Admin sets up a review step, they're required to add in at least one reviewer. While Reviewers can also start their own workflows (and therefore act as an admin for new ones), the majority of government employees use the platform to Review submissions for one or more workflows that an Admin has created. Read more about how Reviewing works on CityGrows here. Any reviewer added to a workflow is automatically also added as an Admin under the Permissions tab.

Government finance and management team member roles: 

Team Members: Teams allow administrators and finance people to access financial transaction information about a set of one or more workflows. Eventually, we'll also add more performance management metrics and aggregated data views at the Team level. The teams page is located by clicking on your account icon and the going to the "teams" selection.

Adding a user to a team is a good way for a management staff member (Department or Division Head, City Manager, or County Administrator) to be able to see across multiple teamplates within a team, without having to receive multiple email notifications or have a dashboard cluttered with lots of processes.

It’s at the Team level that bank account/ payout information is set up and managed, so it's a great place to add representatives from your accounting teams or finance departments who need access to reconcile transactions or see cash flows into your government's bank account.

All workflow payments from one team will go into the same bank account. If your organization has payments that should be sent to different accounts, a different Team should be created for each bank account. If payments from a workflow should go to that account, they’ll need to be in that Team.

Did this answer your question?