CityGrows User Roles, Permissions, and Teams
CityGrows supports the following role types with these associated permissions and access levels:
Applicants (constituents and businesses): This is the role type for anyone 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.citygro.ws." During account setup, applicants submit their 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' "Data and Stats" pages for any public process.
Government account roles on templates:
Admins: Admins are the CityGrows users who set up and then manage processes 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 processes. 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! Ready to get started bringing your processes, forms, and permits online as a CityGrows admin? Our "How CItyGrows Works" page is a great place to start. Admins can also add Reviewers and create Teams (see below).
Reviewers: Admins are the CityGrows users who have been invited to a process 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 processes), sometimes people use the platform just to Review submissions for a specific template. Read more about how Reviewing works on CityGrows here.
Government finance and management 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.
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.
It's also at the Team level that you set the logo and display name for your organization.
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.
Have questions about this article or comments on how it can be improved? Send us a message using the chat icon in the bottom right of the screen.