Skip to main content

5. Set your team up for success

Plan your Yeeflow rollout, configure access to your application, and give teammates a clear first task.

1. Get ready for your Yeeflow launch

Use Projects, Tasks, Project Approval Form, and Reports from the earlier stages to pilot the new process with a small group. Report on metrics with dashboard

1.1 Define your Yeeflow launch goals

Choose a workflow your team can try from beginning to end. For the project example, a requester submits a project, reviewers route it for approval, and an approved project appears in the Projects list.

Explain where people start, who makes each decision, and where they can see the outcome. Pick a measure to track, such as the share of requests submitted through the new form or the time from submission to a decision.

Create a launch document. Record the process, pilot dates, target users, roles, and success measure. Include the application link, support contact, and how to handle requests already in progress.

1.2 Assemble your launch team

Ask a workflow owner to coordinate the rollout and a sponsor to communicate the change. Involve an application administrator to set up access, people who build and maintain the workflow, and teammates who can test it as requesters, reviewers, and dashboard viewers.

Identify the people responsible. For each rollout activity, name who handles access requests, pilot testing, and follow-up. One person can cover more than one role.


2. Prep your application for onboarding

Set up application, list, form, and dashboard access for the pilot. Check what people can open and do with accounts that represent the roles they will use.

2.1 Invite your collaborators to your application

Decide whether people need a workspace role or access to this application. Workspace roles govern workspace management and application creation. Application roles govern work within the selected application. Workspace and application permissions

  • Administrator manages the application structure and settings, including fields, views, and workflows.

  • Editor works with records the user has access to, such as adding or editing items in a data list.

  • Visitor opens the application and views authorized content.

Use specific people, departments, or user groups where the audience is limited. Review any list or resource permissions that further control what each user can open or do.

The Role dropdown in Application users shows Administrator, Editor, and Visitor.

  1. Share. In the application header, open Share. Choose Add from organization for existing teammates or Invite via email if offered. Select the role and confirm the recipients. An invitation to a new user may await system administrator approval. Administrators can also invite people through organization user management. Invite users to your organization

  2. Application users. Open the gear menu and go to Application users in the application settings. Select + New User, choose a role, and select the users, departments, or groups. Use the Role dropdown to review or change an existing grant. Application users and access permissions

2.2 Create customized data views with permissions

In Projects, create a List View named My Projects. In its Data Filters, set Owner equal to Current User. Choose the display fields and make it the default if appropriate for the team.

To keep a broader view for a smaller group, open the existing view’s more menu and choose Edit View. Name it All Projects and set View permission to Specified users, selecting the intended users or groups. If that view is the default, make another broadly available view the default first. Getting started with Yeeflow data views

Use view filters to organize what the view shows. Apply access rules for the underlying list and records in their permission settings, then test access through other views and direct record links.

2.3 Set specific permissions for data lists

Open Projects → More settings → List settings → Permissions. The list inherits application permissions by default. To set access separately, turn off Inherit from Application and review the Administrators, Edit Item, and View Item groups.

Use Advanced Permissions to restrict manual creation and editing. In the pilot, check that a user cannot make a restricted manual change, then complete a test approval and confirm the workflow still creates the project. Manage permissions of a data list

2.4 Set specific permissions for approval forms and dashboards

  • In Project Approval Form, open the form’s settings menu and choose Edit Permissions. Review who can submit the form and who can view submitted forms. Check each with an account that represents the intended role. Edit Approval form settings

  • In Reports, open the dashboard’s more menu and choose Permissions. Set the view audience to All authorized users or Specified users as appropriate. Check that an intended viewer can open the dashboard and see the expected results.

You can also set individual permissions for Dashboards by clicking the More Settings button from the top-right of the dashboard page, and click "Permissions" button to set separate permissions.

2.5 Organize the menus of your application

Open the application settings and select Menu. Select + New Group, name the group Work items, and drag Projects and Tasks into it. Keep Project Approval Form and Reports easy to find. Select Save Changes, then check the navigation as a member. Set the Navigation Menu Bar


3. Introduce your team to Yeeflow

Once the pilot users can complete their tasks, share the new process and give the rest of the team a clear first step.

3.1 Draft your Yeeflow launch announcement

Tell teammates which work moves to Yeeflow, when the change starts, and what they should do first. Include the application link and who can help with sign-in, access, or workflow questions.

Example announcement

Starting [date], submit new project requests through [Project Approval Form]. Reviewers will receive their approval tasks in Yeeflow. Use Projects to find approved requests and Reports to see totals by category, owner, and start month if you have access. Please open [application link] before our walkthrough on [date]. Contact [support contact] if you cannot sign in or find the form.

Replace the links, dates, and contact. Tell the team how to handle requests already underway and where to find a short walkthrough.

3.2 Announce your Yeeflow launch

Have the sponsor or workflow owner share the announcement after the pilot confirms that requesters, reviewers, and viewers can complete their first tasks.

Use the channel where your team gets operating updates, such as a team meeting, email, or chat. Keep the application link and support contact easy to find during rollout.

Did this answer your question?