eradiant docs

Submodule members & roles

Overview

Under Organization → Members you manage invitations, roles, and permissions for your team.

Who can do what? Only organization admins can invite, edit, and change permissions. Other members see the list but cannot add people or edit existing members.

Overview (member list)

The table shows among others:

  • Nickname
  • Email
  • Join date (empty until the invitation is accepted)
  • Organization admin
  • Events, Votings, Contacts, Institutions, Leads, Inventory, Time tracking, Ticketings — each as a compact rights summary
  • Check-in apps admin
  • Manage payment providers

Pending invitations

If someone has not yet accepted the invitation, a letter icon appears next to the nickname (visible to organization admins only). On hover: “Invited, invitation not yet confirmed”.

Search and filter

  • Search bar: searches nicknames
  • Filter: e.g. nickname, email, permissions (by module and individual permissions) and Deactivated

For members who already joined, the edit view additionally shows profile username and join date.

Add members

  1. Click the plus icon (organization admin only).
  2. Enter email and nickname.
  3. Set permissions in the sections below.
  4. Click Save.

Invitation flow: If the person already has an ERADIANT account, the invitation appears on the homepage (eradiant.eu) and additionally by email. Without an account, an account is created or the person is guided through the join process.

Edit members

  1. Click a row or the edit icon (organization admin only).
  2. Adjust nickname and permissions.
  3. Click Save.

Email cannot be changed after creation (display only).

SSO: If the member is SSO-managed, the form is not editable — permissions are managed externally.

Remove members

Direct deletion of members is not provided (privacy / auditability). Instead revoke all permissions and save. You can find deactivated members in the list via the Deactivated filter — deactivation itself is not done via this form.

Fields and permissions

The edit form is grouped into sections (order as in the UI).

Basic data

  • Email: Required for new invitations; read-only afterward.
  • Nickname: Display name in the organization (recommended: first name or first and last name).
  • Profile username and join date: only visible for members who already joined.

Organization

  • Organization admin: Full organization management including members, email configurations, and permission assignment.
  • Manage email dispatch configurations: Create, edit, and delete email dispatch configurations.

Contact module

  • Contact admin: Sets all contact, institution, and lead rights to all (full access).
  • Contacts – View / Create-edit / Delete: each all or none (scope “assigned” is currently not selectable in the UI).
  • Institutions – View / Create-edit / Delete: all or none.
  • Leads – View / Create-edit / Delete: all or none.

Fields depend on each other — e.g. “No contacts view” resets dependent edit and delete rights; Contact admin overrides this and grants full access.

Note: Menu items like Duplicates in the contact module require Contacts – View: all.

Event module

UI note: With event access you see the event module; with event rights event locations and event tags are generally visible.

  • Events – View / Edit / Delete: all, assigned, or none
    • Assigned events: only events where the person is e.g. responsible or event admin.
  • Create events
  • Manage event locations: one permission for create, edit, and delete (internally coupled)
  • Manage event tags: one permission for create, edit, and delete (internally coupled)

Without event access, dependent rights (create, locations, tags) are automatically revoked.

Ticketing module

UI note: With ticketing access you see the ticketing module.

  • Ticketings – View / Edit / Delete: all, assigned, or none
    • Assigned ticketings: only ticketings the person is assigned to.
  • Create ticketings
  • Manage organization-wide check-in apps: Management of check-in devices at organization level (pairing, device list).

Payment providers

UI note: With ticketing access payment providers can be seen; managing them requires the separate permission below.

  • Manage payment providers: Connect and manage providers like Stripe — see Payment provider.

Voting module

UI note: The voting module is only visible if votings may be viewed.

  • Votings – View / Edit / Delete: all, assigned, or none
  • Create votings

Inventory

(If enabled for your organization.)

  • VIEW access
  • EDIT access (requires VIEW)
  • Inventory admin (requires VIEW and EDIT)

Time tracking

(If enabled for your organization.)

  • Own time tracking
  • View time tracking statistics (requires own tracking)
  • Time tracking admin (requires both rights above)

Usage

  • Grant rights minimally — expand as needed.
  • Use assigned scopes for event, ticketing, and voting access when people work on individual projects only.
  • Check pending invitations (letter icon) and remind colleagues to accept on eradiant.eu if needed.