Your First Repository
This walkthrough gets a new team from first login to a usable shared workspace.
Before you start
Confirm these basics:
- you can sign in and open at least one tenant and repository
- Explorer loads without errors
- Search loads for the same repository
- you can create content in at least one folder
If any of these fail, stop and resolve access first.
Step 1: Validate the real workspace surfaces
Open the repository and verify:
- the Explorer shell loads
- Search returns results inside the repository
- at least one focused Explorer view such as Files, Notes, Tasks, or Chats works
If your deployment enables them, also verify Emails, Calendars, Companies, Contacts, or Cases are visible for the right users.
Step 2: Respect the default roots
Many repositories already expose system roots or default content areas such as:
- Files
- Notes
- Tasks
- Chats
- Companies
- Contacts
- Personal folders
Do not randomly repurpose those areas. They reflect how the current platform expects common work to be organized.
Step 3: Seed one real workflow
Inside one project or case folder, create:
- a file or note
- a task list
- a chat thread
- one clear owning folder or record for the work
If your team uses connected mail or calendar, test one realistic linkage there too, such as archiving an email or linking meeting outcomes back to the same folder.
Step 4: Verify view-to-folder consistency
Make sure users can move from a focused view back to the owning context:
- from Files to the real folder
- from Notes to the real folder
- from a Contact or Company to the entity folder
- from a Case row to the case folder and related work
If users can open the view but cannot tell where the work actually lives, your setup is not done.
Step 5: Run operational checks
Before broader rollout:
- confirm path links open for authorized users
- confirm version or activity history appears after edits
- confirm Search can find the content you just created
Done criteria
Your repository setup is good when:
- users know where work lives
- focused views help without replacing folder ownership
- one end-to-end create, discuss, act, and review loop works in the same context