Report Builder
Ever wonder who all is working on a project, or what projects you share across accounts with other Ryan teammates? Now you have the visibility at your fingertips! The team sections allow you to view you teams at the project and account levels. If you are an EM/EP CM/CP +EA you also can manage your team directly from the platform, no need to use workday for this.
Supportive Visual Here
Graphic Recommendations - Have a table that displays user roles and permissions. A Process Map for NURs
Shared Projects
Selecting a Ryan Teammate in your team list will allow you to view what projects you have in common. Selecting “View All” below the Shared Projects, will show all shared projects in the platform, regardless of account. – NEED TO UPDATE THIS-
Supportive Image
Team Member vs. Ryan.com User – (Team User icon vs. User Icon)
Everyone at Ryan will have access to Ryan.com Client Platform. Whether a Ryan user can view projects and interact with data in the platform depends on if they are assigned to any accounts and projects.
Client users, however, can fall into two different categories: Ryan.com User or Team Member. When a client is a Ryan.com user, they have actively created an account in the platform and logged in. We hope that most clients realize the benefits of the platform and become Ryan.com users, but we realize that not every client will want to access the platform. For those client users that do not wish to engage in the platform, they will be displayed on the Team pages as Team Members, with their avatar being their initials with a white background. Users of the platform will not be able to assign items to or mention these Team Members in comments. They are just displayed on the Team pages so that their contact information is readily available to the team. Also, if they decide to become users in the future, they will already have a placeholder in the platform. – **FAQ**
Supportive Image
User Roles/Permissions
Ryan User Roles: (Table)
• Account/Project Team Member – Can interact with almost everything in the platform regarding projects they are assigned to. This will be the most common role for Ryan users • CP/CM/EP/EM – Technically, this is not a role and CPs, CMs, EPs, and EMs will have the role of Account/Project Team Member. However, if they have one of those four roles in Salesforce for their accounts/projects they will have some additional permissions that normal Team Members do not have. These extra permissions include: o Publishing projects to the client o Hiding/Showing Ryan team members to the client (ghosting) o Adding/Removing Ryan team members to projects o Adding/Removing Client team members to projects o Adding/Removing Third-Party users to projects o Managing the roles of their account/project teams • EA – The Executive Assistant role will be predominantly read-only when it comes to the day-to-day functionality of the platform and the project teams’ work. However, they will have similar permissions to the CP/CM/EP/EM in that they can: o Hide/Show Ryan team members to the client (ghosting) o Add/Remove Ryan team members to projects o Manage the roles of their account/project teams o Submit New User Requests for Client users o Rename and publish Contracts o Generate Reports Client User Roles: • Staff – This client role can interact with everything in the platform except they are not allowed to view the Ryan Contracts or Invoices tabs and they cannot access the Manage Team page for the client team. • Management – This client role is similar to the staff role except they have access to the Ryan Contracts and Invoices tabs, and they have the ability to remove other client team members on their team from the platform via the Manage Team page and submit New User Requests. • Clients cannot create Data Requests, Milestones, or Learnings. Third Party Roles - Third parties can ONLY access files
Manage Team
The Manage Team page can be accessed by anyone who is a Client Principal, Client Manager, Engagement Principal, Engagement Manager, or EA on the selected account. The Manage Team page can also be accessed by client users with the Management role. Keeping the teams accurate and up to date will ensure the best client experience. **BP** Managing the team consists of:
Supportive Image
1. Ghosting
Ghosting is the term we use when we are hiding a Ryan team member from the client’s view. If a Ryan user is ghosted on a project, they will have read-only access for that project. On the Team page the ghosted user’s avatar will be a crossed through eye icon, noting that the team member is hidden from the client. To determine if you are ghosted on a project, you can see the crossed through eye icon in the Status column of the Project List in the Projects Overview page. You can also see a Read-Only pill under the project name when you are on any single project page.
Only a CP/CM/EP/EM or EA on the project can ghost or un-ghost a Ryan user. Ryan users should be ghosted if they will be doing work behind the scenes, need to bill time to the project, but it is unnecessary for the client to know that they are on the project.
2. Adding/Removing Ryan Team Members
Ghosting is the term we use when we are hiding a Ryan team member from the client’s view. If a Ryan user is ghosted on a project, they will have read-only access for that project. On the Team page the ghosted user’s avatar will be a crossed through eye icon, noting that the team member is hidden from the client. To determine if you are ghosted on a project, you can see the crossed through eye icon in the Status column of the Project List in the Projects Overview page. You can also see a Read-Only pill under the project name when you are on any single project page.
Only a CP/CM/EP/EM or EA on the project can ghost or un-ghost a Ryan user. Ryan users should be ghosted if they will be doing work behind the scenes, need to bill time to the project, but it is unnecessary for the client to know that they are on the project.
3. New User Requests
New User Requests are the first step to getting a client or Third Parties user access to the Ryan.com platform. NURs can be submitted via the Manage Team page by clients with the Management role, EAs, or CP/CM/EP/EM users. Once a NUR is submitted, it is the responsibility of the Ryan team to assign the client to the specified account and projects within Salesforce. Once that process is done, the CP or CM must go back to the Manage Team page – New User Requests tab and assign the client user a role and approve access to the platform. [Insert Process Map]