Members, teams and roles

Invite people, build teams, define roles, assign practice and certify skills.

An org workspace is people, arranged into teams, with roles that decide what each person can see and do. This page is for the person setting it up.

#Creating an org

From app.revyn.in/auth, choose the organisation sign-up. You become its owner. Org onboarding then walks you through your business profile, what you sell, the documents and URLs to ground the knowledge base on, and a review step that builds your first context pack. Invitations and integrations follow from the setup hub, and every step can be returned to.

#Inviting members

Team → Members → Invite. Enter emails and a role; each person receives a link. Someone who already has a personal Revyn account keeps it; the org account is created alongside and they sign into whichever they need. See Workspaces.

Seats are counted per active member. Pending invitations do not consume a seat.

#Teams

Team → Teams. A team is a named group with a manager. Analytics, assignments, the leaderboard and the risk board can all be scoped to a team. A member belongs to one team; a manager can manage several.

Warning

A manager with no team sees only their own data under "This organisation" headings. Assign every manager a team, or give them the org-wide analytics permission, before they look for their reps and find nobody.

#Roles

Four built-in roles, in descending rank:

RoleCan
OwnerEverything, including billing and deleting the org
AdminManage members, roles, knowledge base, integrations, AI settings
ManagerSee their team's calls and analytics, assign practice, run battles, certify
MemberPractise, use Ask Revyn, see their own data and the leaderboard

Custom roles (Team → Members → Roles) let you define roles between member and manager with an exact permission list, for example a Coach who can read debriefs but not assign, or a Sales Ops role that manages integrations and nothing else. Custom roles cannot exceed a manager's permissions.

#Assignments

Practice → Assign. Choose scenarios or curriculum levels, a team or people, and a due date. Assigned practice appears on the rep's home page and in their scenario picker, and completion rolls up under Insights → Analytics → Assignments.

#Certifications

Team → Certifications. A certification is a bar on a skill line: "Handle the security objection at level 3 with an average score above 80 across three calls". Reps see the bar, attempt it, and are certified when they clear it. Certifications appear on profiles and can gate curriculum levels.

#Lead scenarios

Team → Lead scenarios. Upload or sync a lead sheet; Revyn researches each account and drafts a scenario per account. Review, edit, approve and assign. See Scenarios and prospects.

#RecruitD

Team → RecruitD runs a hiring round on Revyn Voice. Create a round with a scenario, send candidates a link, and every candidate takes the same graded call. Candidates are ranked on the same rubric your reps are, so "would this person survive our discovery call" is answered before the interview.

#AI access

Settings → AI decides what Ask Revyn can reach in your org: which tools are on (CRM read, calendar, research), whether Deep Research is available to members, and whether memory is enabled. Changes apply immediately to every session.

#Activity

Activity is the org's audit trail: who joined, who changed a role, who uploaded a document, who connected an integration, who exported data. It is retained for the life of the org and exportable.

#Removing people

Remove a member from Team → Members. Their calls, debriefs and contributions to analytics stay with the org; their sign-in stops immediately. Their personal account, if they have one, is untouched.

Something missing or wrong on this page? Tell us.