Organizations in Nexterm let you share server entries and identities across a team without giving everyone full admin access to the instance. When you create an organization, you become its owner and can invite other Nexterm users as members. Any server entry placed inside an organization folder is visible to every active member of that organization.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/gnmyt/Nexterm/llms.txt
Use this file to discover all available pages before exploring further.
What organizations control
Shared server entries
Entries scoped to an organization appear in the sidebar for every active member, not just the creator.
Shared identities
Identities can be organization-scoped so that all members can authenticate to shared servers using the same credentials.
Audit settings
Each organization has its own audit configuration covering connection logging, file operations, session recording, and more.
Role-based access
Members have either the
owner or member role. Only owners can invite users, remove members, and update organization settings.Creating an organization
Enter a name and description
Give the organization a clear name and an optional description so teammates can identify it.
Inviting members
Only organization owners can invite users. Invitations are sent by username — the invitee must already have a Nexterm account.Open the member list
Go to Settings → Organizations, select your organization, and open the Members tab.
A user cannot be invited twice. If an invitation is already pending, or the user is already an active member, the invite request returns a conflict error.
Member roles
| Role | Permissions |
|---|---|
owner | Invite and remove members, update organization settings, manage audit configuration, delete the organization |
member | Access organization server entries and identities; cannot manage members or settings |
Organization-scoped server entries
Server entries are scoped to an organization when they are placed inside an organization folder, or when theirorganizationId field is set directly. Organization-scoped entries behave like personal entries from the user’s perspective — you connect to them the same way — but they are visible to every active member of the organization.
Open the organization folder in the sidebar
Expand the folder with the organization’s name. It appears automatically once you are an active member.
Add an entry
Right-click the organization folder and choose New server. Fill in the connection details as usual. The entry is saved with the organization’s ID and becomes visible to all members immediately.
Switching between organizations
You do not need to “switch” organizations explicitly. All organization folders you belong to appear simultaneously in the sidebar alongside your personal entries. If you are a member of multiple organizations, each has its own folder in the tree.Leaving and deleting organizations
- Leaving an organization
- Deleting an organization
Go to Settings → Organizations, select the organization, and click Leave organization. Your membership record is removed and the organization folder disappears from your sidebar.
Organization owners cannot leave their own organization. You must delete the organization instead, or transfer ownership before leaving.
Audit settings
Each organization stores anauditSettings object that controls which events are logged for that organization. Owners can update these settings from Settings → Organizations → Audit.
| Setting | Default | Description |
|---|---|---|
requireConnectionReason | false | Prompt members to enter a reason before connecting to a server |
enableFileOperationAudit | true | Log SFTP file operations (upload, download, rename, delete) |
enableServerConnectionAudit | true | Log SSH, RDP, VNC, and Proxmox connections |
enableIdentityManagementAudit | true | Log identity create, update, and delete events |
enableServerManagementAudit | true | Log entry create, update, and delete events |
enableFolderManagementAudit | true | Log folder create, update, and delete events |
enableScriptExecutionAudit | true | Log script executions run against organization servers |
enableSessionRecording | false | Record terminal session content |
recordingRetentionDays | 90 | Number of days to keep session recordings |