Manage people and access
Create a Member and verify their environment access.
LogForge · Runs in your infrastructure
Before you begin
- Where: LogForge in your browser; no host shell needed.
- Access: Owner or Admin, verified Business license, and available paid-seat capacity for a new person. Owner uses no paid seat.
- Ready: one person and an existing environment they should use.
Start with Member: a Member has no workload access until assigned. Admin can manage the whole installation.
Create a Member
- Open Settings > People & Access > People.
- Choose Create account. Enter First name, Last name, and Username. Select Role: Member.
- Leave Starting team empty for direct access, or choose an existing team whose access you have reviewed.
- Choose Create account once and wait.
- Use Copy password to hand the temporary password over privately, then Dismiss password.
Check: the account appears. Environment access comes only from assignments or the chosen team.
One-time password: it cannot be reopened after dismissal. Exclude it from screenshots, tickets, and shared notes.
Assign one environment
- Select the Member, open Environment access, then Manage access. This opens Add environment access.
- Select the Environment and Access level:
| Choice | Allows |
|---|---|
| View | Authorized status, saved logs, and metrics |
| Operate | Also live logs, workload monitoring, and incident response |
| Workload actions (separate) | Supported lifecycle actions, read-only Files, and operation history |
| Terminal (separate) | Shell commands with the container user's permissions |
- Leave Workload actions and Terminal off unless needed. Operate alone does not grant either.
- Choose Add access, wait, then Done. Review reloaded effective access.
For a team: use Teams > Create team, select it, then Environment access > Manage access. Under Members, select the person and choose Add membership.
Access combines: direct and team assignments add together. Removing one assignment may leave another source of access.
Verify as the Member
- Have the person sign in to LogForge in a separate browser session using their local username and temporary password.
- Complete the required password change.
- Open Settings > People & Access > Your access and check role, team, and environment.
- Check the intended workload's saved logs or metrics. Try live logs only with Operate, and Terminal only with separate permission.
Check: the Member can use the intended environment with the chosen access. Website sign-in supplies no local access.
Change, remove, or recover access
Use Change access > Save access to update a direct assignment. Remove an assignment with its removal action, then recheck effective access. Reductions remain possible when Business expansion is blocked.
Problem: sign-in fails, an environment is hidden, or creation is uncertain.
Why it matters: passwords, assignments, and unfinished account operations need different repairs.
Next step:
- Uncertain creation: use Check creation status or the offered resume action.
- Lost temporary password: use Replace password on the existing non-Owner person. The old password stops working; another change is required.
- Hidden environment: check direct/team access and Business state.
Preserve existing accounts. Do not edit the database or create duplicates. Ordinary People controls cannot reset the initial Owner.