Getting started

Create or join a workspace

Teamtastic is organized around a workspace (your organization). Most teams are invite-only: you register through a link from your Director or Manager, not by creating a random workspace from the marketing site.

Go to app.teamtastic.net/register with the email address on your invite.
Complete email verification if prompted; check spam for the link.
Sign in at app.teamtastic.net/login with email and password, or with Google if your org has Google sign-in enabled.
On first login as the founding user, the setup wizard asks for workspace name, URL slug, timezone, and optional integrations.

If you already belong to another workspace, use the org switcher in the app header to move between them. One account can belong to multiple workspaces.

Roles at a glance

Every person has an org role that controls admin capabilities. Use this table when you are unsure why a button is missing:

Director (shown in the UI; stored as OWNER): billing, invites, wiki publish, integrations, exports, automation rules, and full org data.
Manager (MANAGER): approve PTO, view Insights and Friction on Today, see emergency contacts and leave balances, manage team settings and stale-task rules.
Member (MEMBER): tasks, DMs, channels, PTO requests, and personal settings; cannot change org policy or invite users.

Separately, each team (workstream on the Tasks page) can have a Team Lead who receives escalations when tasks go stale. Team Lead is not the same as Manager: you can be a Member org-wide but Lead on one team.

Custom roles (Business plan)

Business plan workspaces are not limited to the three built-in roles. Directors can define custom roles with tailored permission sets from Settings → Roles. For example, you might create a "Contractor" role that can view tasks and post comments but cannot request PTO or see salary-adjacent data, or a "Team Lead" role with automation rule access but no billing permissions. Custom roles inherit from the nearest default role as a baseline, so you adjust only the permissions that differ. Assign a custom role to any member the same way you would assign Director, Manager, or Member.

Terminology that trips people up

Team in the left nav (/team) = people roster, PTO, and calls.
Team on the Tasks page = a workstream with its own kanban board (e.g. "Engineering").
Workspace = your whole organization tenant; all data is scoped to it.

Invite your team

Directors and Managers send invites from Settings → Team or the Team → Invite tab.

Click Invite member and enter their work email.
Choose org role: Member for most ICs, Manager for people who approve PTO and need Insights.
The invitee receives an email with a one-time link. Links expire for security; resend from Pending invites if needed.
When they accept, they appear on the Team roster and count toward billing seats.

Manager onboarding checklist

After creating a workspace, Directors see a short checklist on Today until dismissed:

Invite at least one teammate.
Upload an org logo (Settings → Profile, company section).
Set an org-wide Zoom or Meet link and configure optional webhooks (Settings → Integrations).
Add a default Zoom or Meet room link for scheduled calls.

Dismissing the checklist does not block anything; it is a gentle nudge.

Member first-day checklist

Set timezone and work hours under Settings → Profile so teammates know when you are available.
Open Navigation & shortcuts and press ? in the app once to see keyboard shortcuts.
Configure notifications, Teamtastic is quiet by default; opt in to mentions, PTO decisions, and DMs.
Skim your team's kanban on Tasks and claim or create your first task.

What members cannot do (by design)

Teamtastic is a governed workspace: members execute work but do not run the org. Members cannot invite users, edit the official wiki, change integration or webhook settings, approve others' PTO, or open Friction/Insights. If you need those capabilities, ask your Director to change your role.

Next steps

Read Navigation & shortcuts for the six main areas, then Tasks & projects for day-to-day work. Org-specific policies (PTO rules, naming conventions) belong in your in-app Wiki.