Workspaces, access, and security
Each workspace in LaraDep is an isolated context with its own servers, access controls, and deployment history. This isolation prevents environment mix-ups, manages team access, and provides an audit trail for every change.
What a workspace contains
- Its own servers — a deployment from workspace A cannot affect workspace B's servers.
- Its own access and roles — who is a member, who can run deployments, and who can only view history.
- Its own sensitive values — passwords and credentials are bound to the workspace and are not shared.
- Its own deployment history — every record is scoped to the workspace, audit scope is always correct.
Roles and access
Access is role-based at the workspace level:
- Who can run deployments and in which workspace.
- Who can view history but cannot trigger changes.
- Who manages workspace settings and configuration.
Adding a new member is an explicit step — it does not happen accidentally. A team member can have access to workspace A but not workspace B.
Safe handling of sensitive values
Passwords, keys, and credentials are never displayed in the interface or returned via API. The deployment history only shows metadata — not the sensitive values themselves. The AI assistant cannot see secret values even if it tries.
Safety checks before deployment
Before every deployment, LaraDep verifies the conditions for running:
- All required values are filled in.
- The server is reachable and credentials are valid.
- The deployment targets the correct server in the correct workspace.
If conditions are not met, the deployment does not start.
Typical workspace structures
- One workspace per client — for agencies and managed services where strict separation is essential.
- One workspace per environment — development, staging, and production as separate spaces.
- One workspace per application — for internal teams managing independent applications.
- Combined model — a combination of the above depending on organizational needs.
Regulated environments
For teams in regulated industries, LaraDep provides deployment history that answers "who, what, when" for every change, workspace isolation, and a documentable process. LaraDep is not a certified compliance solution — it is a tool that makes it easier to follow your team's internal processes.
Next step: Validate your rollout with the first deployment and production checklist.