remFREE organizations can contain multiple members.
Membership allows administrators and technicians to work inside the same tenant while keeping access associated with identifiable user accounts.
Why individual accounts matter
Shared administrator credentials make accountability difficult.
When each person uses their own remFREE account, the platform can associate important actions with the user who performed them.
This improves:
- accountability
- troubleshooting
- administrative visibility
- security auditing
Members and Invites
Tenant administrators can use Members & Invites to manage access to their organization.
A new user can be invited rather than sharing an existing account.
This establishes a direct relationship between the user and the tenant.
Roles
Roles determine what level of access a member should have.
Not every user needs full administrative authority.
The principle is straightforward:
Give people the access required to perform their job without automatically granting every administrative capability.
Tenant boundaries
Membership applies within the tenant.
An authenticated remFREE account should not automatically have access to devices belonging to unrelated organizations.
Authentication answers:
Who is this user?
Tenant membership answers:
Which organization may this user access?
Authorization answers:
What may this user do there?
These are separate questions.
Removing access
When someone should no longer have access to an organization, remove their tenant membership rather than sharing or recycling another person's account.
This preserves the integrity of historical activity while preventing future tenant access.
Administrative activity
Important account and security activity can be represented in remFREE's audit and activity systems.
That makes user administration part of the broader operational record rather than an invisible configuration change.
Recommended practice
Use named user accounts.
Invite technicians individually.
Assign the minimum appropriate role.
Remove access when it is no longer needed.
Review security-related activity when investigating unexpected administrative behavior.
These practices reinforce the same zero-trust mindset used throughout remFREE.