Teams & Permissions

Aqarjia uses a teams-based authorization model to control what each user can access and do within your organization.

How It Works

  • Teams are groups of users with shared permissions.
  • Permissions define what actions a team can perform (view, create, edit, delete) on each module.
  • A user's effective permissions are the union of all permissions from every team they belong to.

Managing Teams

Creating a Team

  1. Navigate to Organization > Teams.
  2. Click Create Team.
  3. Enter the team details:
    • Name -- A descriptive name (e.g., "Finance Team", "Maintenance Crew").
    • Description -- What this team is responsible for.
  4. Configure Permissions by selecting the allowed actions for each module.
  5. Click Save.

Adding Members

  1. Open a team from the teams list.
  2. Click Add Member.
  3. Select one or more organization members to add.
  4. Members immediately inherit the team's permissions.

Removing Members

  1. Open the team.
  2. Find the member in the team roster.
  3. Click Remove next to their name.
  4. Their permissions from this team are revoked immediately.

Permission Modules

Permissions are organized by module:

Module Controls Access To
Properties Property records and management.
Units Unit records within properties.
Tenants Tenant records and information.
Landlords Landlord and beneficiary records.
Leases Lease agreements and terms.
Invoices Invoice creation and management.
Payments Payment recording and history.
Maintenance Maintenance requests and work orders.
Documents Document uploads and management.
Reports Financial and operational reports.
Settings System configuration and lookup tables.

Each module supports four permission levels: View, Create, Edit, and Delete.

Platform Team Templates

Aqarjia includes pre-configured team templates that cover common organizational roles:

  • Property Manager -- Full access across portfolio and finance.
  • Accountant -- Finance-focused access (invoices, payments, reports).
  • Maintenance Coordinator -- Operations access (maintenance, work orders, contractors).
  • Viewer -- Read-only access to all modules.

Templates can be used as-is or customized after creation.

Best Practices

  • Principle of least privilege -- Grant only the permissions each team needs.
  • Separate concerns -- Create distinct teams for finance, operations, and administration.
  • Audit regularly -- Review team memberships and permissions quarterly.
  • Avoid single points of failure -- Ensure critical functions have multiple team members.

Organization owners always have full access regardless of team membership. The teams system only restricts members.