Zemtu
  • Introduction
  • Features
    • Translations
    • Branding and customizations
    • Reservation GUI
    • Carsharing Group Overview
    • Admin interface
    • Billing module
    • Accreditation
  • Changelogs
    • Backend
      • 2025
    • Desktop
    • Mobile
  • Core
    • Introduction
    • User Roles
      • Organisation level
      • Accreditation Circle level
      • Carsharing Group level
    • Master data
      • User
      • Vehicle
      • Carsharing Group
      • Membership
      • Reservation
      • Organisation
      • Accreditation
      • Accreditation Circle
      • Chip card
    • Guides
      • First steps
      • Manage memberships
      • Manage reservations for other users
      • Change to user
    • Customization Options
  • Billing
  • Introduction
  • Workflow
  • Master data
    • Payer
    • Billing cluster
    • Reservation rate
    • Vehicle rate class
    • Rate plan
    • Tariff exception
    • Package
    • Package assignment
    • Payment adoption
    • Service provider
    • Manual payment
    • Invoice
    • Invoice run
    • Turnover guarantee
  • Guides
    • Initial billing setup
    • Monthly billing workflow
    • 🎫Coupons
  • On-board units
    • Convadis
      • Guides
        • First level support
        • Connect Convadis CBox
        • Order chip cards
        • Manage chip cards
    • INVERS
      • Chip card reader
      • 🌂Umbrella feature
  • API
    • REST
    • GraphQL
  • Mobile
    • 🌂Umbrella feature
Powered by GitBook
On this page
  • Permission matrix
  • Pseudonymization
  • Edit restrictions
  • Workflow
  • User roles
  1. Core
  2. Master data

User

PreviousMaster dataNextVehicle

Last updated 2 years ago

Regular users sign in and make reservations. Additionally users with special can use the Admin Interface to manage .

Permission matrix

Role

Add

Edit

Pseudonymize

OrgAdmin

x

x

x

Accreditor

.

GroupAdmin

x

.

x

Pseudonymization

Users with associated objects cannot be simply deleted. Instead admins can schedule pseudonymizing the user. Then the user will be inactivated and the user’s data will obfuscated.

Edit restrictions

  • Accreditor: Restricted to users who applied for accreditation.

  • GroupAdmin: Restricted to users who were created by GroupAdmin user.

Note: Users that already have associated objects (e.g. reservations) must not be deleted. This is to prevent that relevant data is lost. To deactivate a user deselect the active option for the user in the Admin Interface. This prevents that the user can sign in.

Workflow

If self-registration is enabled for an organisation, new users can create accounts using the signup form. Otherwise only users with special can add new user accounts.

User roles

For users to become GroupAdmin of a Carsharing Group two steps are needed:

  1. User object must have special role GroupAdmin

  2. Carsharing group must define this user as GroupAdmin

roles
master data
roles