Skip to content
suparko
Talk to us

Project management and team collaboration

Projects, tickets, chat and files. One connected workspace.

Suparko gives every project a shared home: tickets with clear owners, conversations that point at the work, files that keep their versions and a portal where clients approve deliverables. Permissions are checked on the server, every time.

Talk to us Explore the product

Already a member? Log in to your workspace

Built into every workspace

  • Server-enforced permissions
  • Client approvals
  • Opt-in AI with sources
  • Linear CSV import
  • Ticket-only MCP

One workspace

Everything a project needs, already connected.

Plan in Work, discuss in Chat, keep files in Drive and record decisions next to the tickets they affect. Each part has its own focused workflow and its own illustrated guide.

Work & projects

Board and list views of the same tickets, with priorities, labels, relations, bulk changes and saved views.

Team chat

Channels, direct messages and threads. Ticket references are checked against each reader’s access.

Drive & files

Your Drive and Shared Drive, with image, video and audio previews, version history and explicit sharing.

Project knowledge

Briefs, pages and decisions for each project. Every save keeps a permanent revision.

Planning

Project dates, milestones, workload by assignee, blocked work and an eight-week delivery trend.

Check-ins & notifications

Mentions and updates in one place, plus scheduled check-ins, overdue reminders and weekly summaries.

Work & projects

Tickets the whole project can follow.

Every request becomes a ticket with an owner, a priority and a place in its team’s workflow. Review the same records as a board or a list, and change many at once without losing the history.

  • Five priority levels, labels and due dates
  • Sub-issues plus blocks, blocked-by and duplicate relations
  • Bulk changes to up to 100 tickets at a time
  • Workspace and personal saved views
Explore Work & projects

Team chat

Conversations that point at the work.

Discuss in channels, direct messages and threads, then reference the ticket instead of retyping it. Readers without access to that project see “Ticket not available”, never the restricted details.

  • Channels, group and direct messages
  • Threads, mentions and reactions
  • Image and video previews in the conversation
  • See who is active now or when they were last seen
Explore Team chat

Client portal

Client approvals on the exact file version.

Publish a saved file version to the clients you invite. They see only what you share with them, download that exact file and respond. Each response is tied to the file’s digest, so replacing the Drive file later never changes what was approved.

  • Invited client accounts see only their shared versions
  • Approve, request changes or comment
  • Owners get an in-app alert when an approval changes
  • No internal tickets, chat or Drive listing in the portal
How client access works

How it works

From kickoff to sign-off in four steps.

A typical project in Suparko, from the first team setup to the client’s approval.

  1. Set up the project

    Create a project, link the teams that deliver it and invite members with a private link.

  2. Capture the work

    Turn requests into tickets with owners, priorities and due dates, or import Linear issues from CSV.

  3. Decide in context

    Discuss in Chat, reference the ticket and record the outcome as a project decision.

  4. Review and deliver

    Clients approve exact file versions in the portal while Planning shows milestones and blocked work.

Access and AI

Access you can explain. AI answers you can check.

Workspace roles plus project, team and file access are enforced on the server for every read, search, reference and change. AI follows the same rules.

Server-enforced permissions

Restricted work stays out of search, pickers and references.

Suparko AI, opt-in

Read-only answers from records you can access, with linked sources.

Ticket-only MCP

ChatGPT via OAuth, or compatible clients with a workspace key.

Import & export

Portable Suparko archives and Linear issue CSV import.

See how ticket MCP is scoped

Solutions

Built for the teams that ship together.

Product, engineering and operations teams share one workspace while each keeps the workflow that fits its job.

Product teams

Give the team a shared place to decide what matters, explain why and track the next step.

  • Project briefs and decision records
  • Milestones and blocked work in Planning
  • Client approvals on exact file versions

Engineering teams

Keep the problem, the work and the discussion together as a task moves through the team's workflow.

  • Blocks, blocked-by and duplicate relations
  • Bulk updates and saved views
  • Ticket MCP for compatible AI clients

Company operations

Create a consistent place for the team to communicate, organize materials and track responsibilities.

  • Recurring tickets and templates
  • Scheduled check-ins and weekly summaries
  • Shared Drive with explicit sharing

Learn the workflow

From your first sign-in to your team’s next task.

Public, step-by-step guides for account setup, projects, conversations and ticket MCP. Every example uses a fictional workspace.

Browse all guides

FAQ

Questions teams ask first

What Suparko is, how work is organized and how to get started. For more, read the full questions and answers.

What is Suparko?

Suparko is a team workspace for project management, issue tracking, team chat and file sharing. Teams organize work in projects, track tickets, discuss decisions, keep files together and share deliverables with clients for approval.

How are projects, teams and tickets organized?

A workspace contains projects. Each project can involve multiple teams, and tickets carry their project and team context. Members work with the projects and tickets available to their account.

What can I do with a ticket?

Add a description, owner, priority, due date, labels and attachments. Discuss progress in comments, add sub-issues and relations such as blocks or duplicate, update up to 100 tickets at once and review them in board or list views and saved views.

Can my team discuss work and share files?

Yes. Chat supports channels, direct conversations, reply threads, mentions and attachments. Drive provides personal and shared file areas with folders, version history and previews for images, video and audio. Workspace storage capacity applies.

Can clients review work in Suparko?

Yes. A project manager publishes a saved file version to the client portal. Invited client accounts see only the versions shared with them, download the exact file, comment and, when approvals are enabled, approve it or request changes.

How does Suparko work with AI?

Suparko AI is off by default. When an administrator enables it, members can ask questions and receive read-only answers drawn from records they can access, with links to the sources. Separately, compatible external AI clients can use the ticket-only MCP endpoint through OAuth or a workspace API key.

How can I start using Suparko?

Contact Suparko to discuss your team and workspace requirements. Administrators invite members with a private link that expires after 24 hours; Suparko does not send invitation emails automatically. Existing members sign in and can follow the first-day guide in Resources.

Next step

See how Suparko fits your team.

Tell us how your projects run today. We’ll walk through the workspace with your workflow in mind.

Talk to us Browse the guides