Team roles explained

Roles vs people In Anymelk, a role is a named bundle of permissions. People receive one or more roles; permissions combine to determine what they see and do. Examples your team might define: Agent — create and edit own listings and buyer requests, read customers Senior agent — above plus edit others’ records Approver — review pending listing and buyer request changes Office manager — team invites, categories, billing read Owner — full team settings Names are yours to choose — the platform does not force “Agent” literally. Why roles exist Real-estate teams separate duties: Junior agents should not delete inventory or change team billing Approvers need read access broadly but write only on review actions Support staff may need customers read without property create Roles encode these boundaries so the sidebar stays consistent for each person. Common permission themes Permissions group into practical areas. You will see labels like these in the role editor: Properties Read — view listings and filters Create / update — add and edit listings Approve — accept or reject change proposals Manage categories & amenities — edit team lists Buyer requests Read / create / update — parallel to properties Approve — gate demand changes Customers Often tied to property/buyer request read — customer access follows deal access Team & organization Manage members — add/remove people Invite — send email invitations Manage roles — edit permission bundles Manage settings — team profile, approval rules, branding Approvals & activity history Approvers see Approvals → Review queue Activity history read may be manager-only Reminders & tasks Read/create reminders for follow-ups Task/project permissions for work management area Billing Billing read — subscription, invoices (no payment actions unless also granted) Payment history read — wallet transaction history Your team composes roles from these building blocks — there is no single global “admin” role inside the team unless owners create one. Multiple roles on one person Members can hold multiple roles . Permissions combine — if any role grants a capability, the member has it. Example: Agent + Approver = daily listing work plus review queue access. Avoid piling redundant roles — one well-designed Senior role is easier to check than three overlapping ones. What agents experience The app is permission-aware: Missing property create ? No “Add property” button. Missing approve ? Approvals queue hidden; My submissions may still appear if you submit changes. Missing team invite ? Invitations tab absent. The sidebar hides what you cannot use — but the server still enforces permissions. Assign roles correctly. Editing roles safely From Team → Roles : 1. Select a role 2. Toggle permissions grouped by area 3. Save Changes apply to all members with that role immediately. For large shifts (new Approvals area), announce before saving so nobody is surprised by new sidebar items. Create new roles instead of repurposing old ones when job functions diverge — “Agent 2024” vs rewriting “Agent” preserves clarity in conversation. Suggested patterns | Role | Guidance | |------|----------| | Trainee | Read-mostly + create draft listings | | Agent | Full create and edit on owned work, no approvals | | Lead | Approve + manage categories | | Ops | Team + billing read + storage | Start minimal; expand when someone hits a real wall — not preemptively for every hypothetical. Plain-language FAQ “I cannot see Billing.” Your roles lack billing read — ask the owner. “I edit listings but changes stick in pending.” You have create, not auto-publish — your team uses approvals. Submit and wait, or get approver role. “Can I see other agents’ customers?” Depends on read scopes your owner configured — often yes within the team for collaboration. “What are organization roles?” Named permission sets your owner assigns inside your workspace — they control what you can see and do in Anymelk. Roles are the contract between agency policy and software behavior — invest an hour defining them well and save months of access confusion.