Workspace Defaults
Set sensible defaults so new work and users start from a consistent baseline.
#Purpose
Reduce repetitive setup by defining defaults once.
#When to use this
During setup and when standardizing how the team works.
#At a glance
| Detail | Value |
|---|---|
| Required permissions | Manage-organization (CEO or admin) |
| Administrator level | CEO / Admin |
| Portal areas used | Settings, Workspace |
#Step by step
1
Open Settings
Go to the workspace settings.
2
Set your defaults
Configure the default behaviors available.
3
Save
New activity follows the defaults.
#Approval points
No formal approval gate
This administrative action does not require a separate sign-off, but review carefully before applying changes.
#Security notes
Security considerations
- Defaults that affect access or notifications should follow least-privilege and avoid over-notifying.
#Best practices
- Keep defaults simple.
- Review them as the team grows.
#Common mistakes
- Over-configuring defaults early.
- Forgetting defaults exist when troubleshooting behavior.
#Troubleshooting
| If this happens | Try this |
|---|---|
| Behavior is not what I expect | Check the relevant default in workspace settings. |
#FAQ
Can users override defaults?
Where personal preferences exist (like notifications), users can tune their own.
#Keep exploring
#Related admin guides
#Business modules & workflows
Getting Started
Initial setup.
Platform Overview
How the OS fits together.
Knowledge Base
Task-level how-tos.
Business Workflows
End-to-end processes.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?