This guide describes the intended administrative workflow for the ASMS Workspace cloud service. Exact modules, integrations, limits, and advanced controls can vary by subscribed plan and enabled workspace configuration.
What ASMS Workspace is designed to manage
ASMS Workspace is subscription-based project and task management software for small businesses and teams. It is designed to centralize projects, tasks, ownership, due dates, collaboration context, and operational reporting in a browser-based workspace.
Recommended first-time setup
- Create or provision the workspace.Confirm the organization name, primary administrator, plan, billing contact, and timezone.
- Define your structure.Agree project naming, statuses, priorities, and ownership conventions before importing or creating large amounts of work.
- Invite a pilot group.Start with administrators and a small manager/member group to validate permissions and workflow.
- Create one pilot project.Test tasks, due dates, status updates, views, notifications, and reporting end to end.
- Review access and launch.Confirm the correct people can see and change the correct information before wider rollout.
Cloud access and browser requirements
No local application server is required for the cloud edition described by this website. Users access the service using a supported modern browser and an internet connection.
| Area | Recommendation |
|---|---|
| Browser | Current Chrome, Edge, Safari, or Firefox release |
| Network | Reliable HTTPS internet access |
| Accounts | Unique user account per person; avoid shared administrator credentials |
| Administration | At least two trusted administrators for continuity |
| Data preparation | Consistent project names, owners, statuses, and due-date conventions |
Configure the organization workspace
Before creating large numbers of projects, define the settings that affect every team. A clean foundation reduces inconsistent reporting later.
- Organization / workspace display name
- Primary timezone and working week
- Default project statuses: Planned, Active, On Hold, Completed
- Task priorities: Low, Normal, High, Urgent
- Standard naming format for projects
- Administrator and billing contacts
Use least-privilege access
Give each person only the access needed for their responsibilities. Keep administrator access limited and review it periodically.
| Role pattern | Typical responsibility |
|---|---|
| Workspace Administrator | Workspace configuration, users, high-level governance and administrative controls |
| Project Manager | Create/manage projects, assign tasks, update milestones and review reports |
| Team Member | Work on assigned projects/tasks and update progress |
| Viewer / Stakeholder | Read-only or limited review access where enabled |
Offboarding
When a user leaves, transfer ownership of open work, disable access promptly, verify shared project responsibilities, and retain business records according to your organization policy.
Build projects around outcomes and ownership
Each project should have a clear purpose, owner, target dates, status, and set of tasks. Avoid creating projects for work that is too small to require separate reporting.
Project: Customer Portal Refresh
Owner: Project Manager
Status: Active
Target date: 18 Nov
Milestones: Plan → Build → Review → Launch
Tasks: assigned to individual owners with due datesMake every task actionable
A useful task normally has one accountable owner, a clear action, due date where appropriate, priority, and status. Update tasks as work changes rather than using comments as a substitute for status.
Choose the right view for the question
Use a board for workflow movement, a list for operational review, timeline/calendar views for date-driven planning, and reporting for management summaries. Availability of advanced views can vary by plan.
Keep project context with the work
Use project/task updates to record decisions, blockers, and handoffs. Reference the responsible owner and expected next action so conversations remain operational rather than becoming an unstructured message feed.
Use notifications for action, not noise
Where notification controls are enabled, prioritize assignment changes, approaching due dates, overdue work, direct mentions, and important project status changes. Avoid subscribing every user to every event.
Review delivery with consistent measures
Useful recurring measures include active projects, project status, task completion, overdue tasks, work by owner, due-date risk, and workload distribution. Export or advanced report options depend on your enabled plan and configuration.
Confirm all active projects have a current status, overdue work has an owner/action, completed work is closed, and projects due in the next period have realistic target dates.
Plan integrations around a source of truth
Integration availability is tenant and plan dependent. Where enabled, common patterns can include calendar/email connections, API-based synchronization, webhooks, file import/export, or links to external business systems.
Document the data owner, direction of synchronization, fields exchanged, authentication method, retry/error handling, and what system remains authoritative when records conflict.
Apply basic workspace governance
- Use individual accounts rather than shared credentials.
- Limit administrator access to trusted staff.
- Use strong unique passwords and organization-supported identity controls where available.
- Review inactive users and access periodically.
- Remove access promptly during offboarding.
- Do not store passwords, card numbers, or unrelated confidential secrets inside project descriptions or comments.
Specific security features such as SSO, MFA, audit exports, retention, or API controls should only be described as enabled after they are actually configured for the subscribed service.
Keep website and checkout terms consistent
The public website currently describes monthly Starter, Professional, and Business plans with a 1-day free trial and $0 setup fee. Your hosted checkout configuration should match the displayed plan price, currency, trial, renewal, and cancellation terms exactly.
For subscription or billing questions, contact ASMS GROUP PTE. LTD. at +65 9292 8920.
Recommended administration routine
| Frequency | Review |
|---|---|
| Daily | Failed access requests, urgent overdue tasks, major project blockers |
| Weekly | Active project status, unassigned work, due dates, overloaded owners |
| Monthly | User access, project archive/closure, reporting quality, subscription/billing contacts |
| Quarterly | Role model, integrations, workflow conventions, dormant users, documentation |
Common checks before contacting support
Checkout button says the plan is unavailable
Confirm the corresponding Stripe Payment Link is configured in assets/js/config.js and that the URL starts with HTTPS.
A user cannot see a project
Check whether the user is active, belongs to the intended workspace/team, and has the required project or role access.
Reports look incomplete
Check that projects use consistent statuses, owners, and task completion data. Reporting quality depends on operational data being kept current.
Login on this public site does not authenticate
The included login interface is a portal preview for the static website. It intentionally does not transmit credentials. A real authentication service must be connected before production portal access is enabled.