Canonical page: https://tellenze.com/help/getting-started

# Your first steps in Tellenze

Find your workspace, define a useful work item, and move it toward an outcome.

## Find your workspace

Sign in with the account that has been invited to your workspace. Joining the public waitlist does not create a workspace membership. If you cannot sign in, ask your workspace administrator to check your invitation and account access.

Home is your starting point. Open **Work** in the sidebar to find Projects, Teams, Views, and available milestones. **Knowledge** contains your team’s documentation. Select your avatar in the header to open the account menu. Choose **Account settings** for appearance, notifications, machine profiles, and MCP connections. The same menu includes **Help center**, **Admin** for administrators, and **Sign out** on desktop and mobile.

Home’s work counters open the work behind each total. Select **Favourite projects** to open Projects with **Favourites** enabled. Select **Your queue**, **Work in progress**, **Completed this week**, or **With due dates** to open **Your work** on the matching tab. Switch tabs inside the dialog and use **Previous** and **Next** to browse every matching item. Select a work item to open its details; press Escape or the close button to return to Home.

The work tabs include your assigned items across active projects and teams you can access, excluding archived work. **Your queue** includes all open stages; **Work in progress** follows each workflow’s in-progress stages. **Completed this week** uses your saved timezone and lists the newest completions first. **With due dates** counts assigned open work with any due date, including overdue work and dates far in the future. **My work** remains a preview of up to 50 items; **Your queue** lets you browse beyond that preview.

**Work risks** uses that full assigned open queue. Overdue means the due date is before today in your saved timezone; Next 7 days includes today through the following six calendar days. Blocked work can also be overdue or due soon. The preview shows each relevant work item once, even when several reasons apply. If there are no matching items, the card explains that your open queue has no overdue, blocked, or near-term work.

**Favourite projects** shows project-wide open, in-progress, blocked, and overdue counts across work you can see, including work assigned to other members. Only active projects you can access appear, in your favourite order. Star a project from Work to add it. On a wide screen, Home places My work beside Work risks and Favourite projects, with Looper, upcoming work, and notifications in a compact rail. The same information remains available in the familiar stacked layout on smaller screens.

On Starter and higher subscriptions, **Signals** shows workspace-wide counts for Raw, Grouped, In progress, In review and Completed. Select a count to open that board view, or choose **Open Signals** for the full board. **Next to review** highlights up to three signals, prioritizing resolution confirmation, then grouped evidence, then new reports. Each preview opens the signal and shows only project labels and suggestions you can access. Completed uses the visibility window in Admin Settings. The section is hidden when there are no active, recently completed or filtered signals. Use the chevron beside **Open Signals** to collapse or expand the section; your choice is remembered for your account in this browser. **Open Signals** remains available while collapsed. Processing notices and the filtered-report link help you spot a stalled pass or review noise; opening Home does not run Looper. See the [Signals guide](https://tellenze.com/help/signals).

Some features are enabled per installation. If a control described here is missing, check with your administrator before trying another URL. A guide does not grant access to a feature or private project.

## Follow your Home onboarding

**Get started with Tellenze** appears between Home’s greeting and counters on every installation. Administrators learn to connect an MCP client, create a project, invite teammates, create a document, and create a work item. Members connect a client, find and favourite a project, then create a document and work item. The order is a recommendation: you can start any checkpoint.

Choose **Start walkthrough** for guidance alongside the existing screens. You still choose what to create and submit each form yourself. Document and work-item lessons carry your selected project forward; use the project selector to choose another accessible location. If no project is available, request access or create one from Work where permitted, then retry or skip.

Progress starts fresh for existing and new members. Newly saved work counts once it is verified, including work created by an authenticated agent acting for you after enrollment. Documents need saved content; work items need saved context and acceptance criteria. Invitations count after a successful send without waiting for acceptance. An existing usable MCP connection or project favourite can count after you open its lesson; use **Check progress** to recheck your connection after authorization.

**Skip for now** records a skipped checkpoint separately from a completed one. **Pause walkthrough** or Escape stops guidance and leaves the current form and its draft open. Collapse the card to keep only a compact progress row. Once all applicable checkpoints are completed or skipped, choose **Finish onboarding** to remove the card from Home.

When workspace gamification is enabled, each newly verified checkpoint earns **5 points** by default. These rewards appear in your profile’s **Recent wins**. Skipping, replaying or choosing Finish onboarding does not award extra points. Checkpoints completed before rewards were available or while gamification was disabled are not rewarded later.

Return to **Account settings → Preferences → Onboarding** to resume skipped steps or replay lessons. Replaying keeps completed progress. Changing roles preserves common progress and updates the applicable journey. Completed checkpoints remain learning milestones even if a resource is later archived or a connection is revoked.

## Define your first work item

1. Open an accessible Project or Team from Work. Choose the owner that is responsible for the outcome.
2. Create a work item with a title that describes a result, such as “Customers can download their receipt”. Choose the work type that fits the request.
3. In **Definition**, explain the context and add acceptance criteria: observable checks that tell the team when the work is complete.
4. Set the assignees and complexity in Details. Add a due date only when there is a real deadline.
5. Link relevant documents and related work so the next person has enough context to start.

For example, a receipt task might require a download button, a PDF containing the correct order details, and a useful error message if the receipt cannot be loaded. Those are better completion checks than “Build receipts”.

## Move the work forward

Move the item through the stages configured for its Project or Team. Stage names can differ between workflows. Use the in-progress stage when execution starts and the review stage when another person or release step must still check the result.

Use **Conversation** for questions, decisions, and progress that other contributors need. Mark the work blocked when a dependency prevents progress and explain what would unblock it. Watching an item helps you follow its updates.

Before completing the item, check its acceptance criteria, record the delivery result, and link the output. Completion should describe an achieved outcome, including verification that matters to the next reader.

## Build a repeatable habit

Start with a small amount of clearly defined work. Use a Focus group for a bounded commitment and a milestone for a larger result with a target date. Views let you find relevant work across its original owners.

When a structure repeats, turn it into a template. When the same event should repeatedly cause the same supported action, use an automation. The following guides walk through both.

## Work across multiple workspaces

Use the workspace address to sign in. From the public Tellenze site, choose **Sign in** and enter the workspace name in its address, such as `bewitt`. Each workspace chooses its own available methods; one may use Google while another uses email/password.

Expand **My workspaces** in your account menu. When you have multiple linked workspaces, choose another workspace to open its home page directly; you’ll be asked to sign in there if needed. Choose **Manage** to view your connections or link another workspace. Manage is available even when you have only one workspace.

To connect an existing membership in another workspace, start the link from Manage, sign in to the other workspace when prompted, and confirm the connection on both sides. Matching email addresses alone do not join accounts. Linking keeps each workspace’s roles and sign-in policy intact.

Under **Account settings → Sign-in methods**, you can explicitly link another provider enabled by your workspace after a fresh sign-in. If your membership is suspended or your workspace disables a method, ask its administrator for help.