Here’s the homepage draft. Let’s keep feedback in this thread before Friday’s review.
Homepage draft.pdf240 KBCoplace on your own servers
Your team’s workspace.
Your infrastructure.
Evaluate Coplace on your infrastructure for messaging, shared notes, and task tracking. Plan data location, network access, and operating responsibilities with your technical team.
launchOctober launch
Playing one sample message and reply.
Enter to send · Shift + Enter for a new line
Make four decisions before deployment.
Choosing a server is the start. User access, data services, and operations need to be planned together.
Your network and access
Map domains, HTTPS certificates, user connection paths, and network requirements for calls together.
Where your data is stored
Define the location of message data, file storage, logs, and backups. Include access owners and retention requirements in the same plan.
Capacity and services
Review user and file load, concurrent calls, and monitoring requirements. Consider application and calling infrastructure separately.
Updates and rollback
Agree on a test environment, release windows, backup restores, and who handles rollback when an update needs to be reversed.
Define where each service runs and who owns it.
Document the deployment scope around messages, files, and calls. Review these topics during technical discovery, with the final architecture shaped by your requirements.
ScopeWhat to planReview in the pilot
Application and messagesDomains, user access, and data servicesSign-in, channel access, sending messages, and reopening history
FilesStorage location, capacity, and access boundariesUpload, sharing, and authorized access
CallsReal-time services and network connectionsAudio, video, and screen sharing
OperationsMonitoring, backups, updates, and supportRestore procedures and owners
Pilot and rollout
Test the deployment plan with your team’s daily work.
Choose a real team and project. Keep technical acceptance criteria and day-to-day findings together on a shared page.
- Scope and owners
- Document pilot users, services, and an owner for each open question. Agree on the responsibilities of your technical team and the Coplace team.
- Use and acceptance
- Try messaging, file sharing, and calls on your organization’s network. Keep findings, acceptance criteria, and remaining work in the same plan.
- Preparing for rollout
- Agree on update windows, support contacts, and restore procedures. Assign outstanding questions to their owners before rollout.
welcome
Open an example
The first-week plan
Our plan for welcoming new teammates.
Decision
We’ll start the first day with introductions and a short workspace tour.
Try editing the decision in this sample note.
Let’s keep the first-week guide in this channel’s Canvas tab.
What comes next
| Task | Owner | Status |
|---|---|---|
| First-week guide | Maya | In progress |
| Channel descriptions | Alex | In progress |
| First-day schedule | Jamie | To do |
Welcome tasksRelated link
Welcome planning notes
Monday · People and culture team
Agenda
- First-week guide
- Team channels and the people who can help
- The first-day schedule
Decision
We’ll add the team channels and people who can help to the guide. New teammates will tour the workspace together on their first day.
Try editing the decision in this sample note.
Guide: Maya. Channel descriptions: Alex. Schedule: Jamie.
Project planRelated link
Questions about deployment
Where should deployment planning begin?
Start with user count, concurrent calls, network access, storage, and your operations team. During technical discovery, we define the service scope and acceptance criteria together.
Do files and calls run on the same server too?
The application, database, file storage, and real-time calling services have different technical requirements. Their placement is defined together with your network and capacity plan.
Who manages updates and backups?
Responsibilities depend on your deployment and support scope. Before launch, agree on update windows, rollback steps, and backup and restore procedures in writing.
Which apps do people use to connect?
You can evaluate user access through the web and desktop apps. Domains, session policies, and client rollout form part of the technical plan.
Let’s review your infrastructure plan.
Share your requirements. We’ll work through deployment options, ownership, and evaluation steps together.