Permissions, roles, plans and prefixes

Create or update a Real Estate permission assignment

Select staff/role and supported feature capabilities.

Audience: CRM staffPermission: real_permission: Create or EditModule v1.0.0
Exact navigationAdmin Area → Settings → Permissions → Add/Edit
Before you begin
  • Use an account with real_permission: Create or Edit and confirm the intended record or setting before making a change.
  • Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
  • Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Select staff/role and supported feature capabilities. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

  1. Open Admin Area → Settings → Permissions → Add/Edit.
  2. Choose the New, Add, Create or Start action exposed on that screen.
  3. Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
  4. Save or submit the form once; correct any validation message rather than bypassing it.
  5. Open the resulting record and verify its number, status, totals, files, activity and downstream links.

Fields, choices and supported possibilities

Exact actionCreate or update a Real Estate permission assignment
Exact navigationAdmin Area → Settings → Permissions → Add/Edit
Module version1.0.0
Access rulereal_permission: Create or Edit
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.

Code-backed validations and workflow rules

  • The modal posts permissions[feature][] values.
  • Save only capabilities appropriate to the user’s role.

Expected result and verification

  • The supported create or update a real estate permission assignment flow completes without bypassing permission or validation checks.
  • The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
  • Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

  • Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
  • Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
  • Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
  • Test settings and automated jobs with controlled records before production-wide use.