Product Specification
Version 1.3.1
Last Updated: October 3, 2026
Language priority: For the Türkiye region, the Turkish version is the main version. If the English translation differs, the Turkish version controls to the extent permitted by applicable law.
This document describes the current product model and principal capabilities of TeamWorkStation (TWS) for product information and user orientation. It is informational. The Terms of Service, Privacy Policy, and, where applicable, the Data Processing Agreement govern legal rights and obligations. Actual feature availability may depend on the plan, deployment, permissions, and interface configuration. This is not a Subscription and Billing Terms document.
TWS is a web-based collaboration platform for individuals, families, teams, and organizations. It provides user accounts, collaborative Boards, hierarchical Cards, forms, files, comments, announcements, notifications, approval workflows, and selected public publishing features.
The product is accessed through supported web browsers. The available hostname, deployment, and public website configuration may vary by installation.
TWS supports account authentication with an email address and password, as well as Google Sign-In where enabled by the deployment. Password reset and additional account-security controls, including two-factor authentication, may also be available.
Users may create personal accounts and, subject to authentication and permissions, may:
Users may manage supported profile and account settings, including their password and available authentication methods. Account and security features are subject to the deployment configuration and applicable verification requirements.
A Board is an isolated workspace that may represent a project, department, organization, family, or another collaborative environment.
A Board may contain:
Users collaborate in a Board after accepting an invitation or otherwise receiving the required authorization. Board owners and authorized roles manage access and Board-level settings within the permissions provided by TWS.
TWS uses Board-scoped role-based permissions. The supported Board roles include member, reporter, coordinator, manager, and owner. The permissions of each role determine whether a user may view, create, edit, delete, assign, comment on, manage files, manage Templates, manage Tags, publish content, or administer Board settings.
Permissions apply to the relevant Board and do not automatically grant access to another user’s private data or another Board.
Templates define reusable structures for operational Cards. A Template may include custom forms, default Tags, assignees, approval workflows, folder assignments, reporting configuration, and hierarchical Card relationships.
Creating a Card from a Template clones the supported Template hierarchy and its operational configuration. Comments are not copied, so each created Card tree has its own collaboration history.
Cards represent work items, documents, requests, records, or other structured information. Cards may contain child Cards, forms, files, comments, emoji reactions, and approval data. Authorized users may move Cards and branches within a hierarchy.
Where supported and enabled, Card content may be encrypted. Encryption can restrict access and some operations until an authorized user unlocks the Card; the exact behavior depends on the Card state and applicable permissions.
Templates may define multi-level approval workflows. A level may specify a quorum, optional approvers, and required approvers. Approval behavior is controlled by the Template and the Board permissions.
When configured, completing the required approvals may lock a Card. Editing a Card or certain related settings automatically removes its previous approvals so that approval status reflects the current content.
Board administrators may configure reusable Tags and Template forms. Supported form fields include text, rich text, integer and decimal numbers, dates, times, files, email addresses, phone numbers, toggles, checkboxes, radio buttons, and selection lists. The supported field set may expand over time.
Boards provide permission-controlled file and folder management. Authorized users may upload, download, rename, organize, and manage files according to their Board permissions. Cards may also have a dedicated file space associated with the Card.
Files are stored using the deployment’s configured local filesystem or compatible object storage provider. The current production deployment is configured for AWS's Istanbul Local Zone, Türkiye. Object Storage is not an automatic backup service. The local development configuration uses the local filesystem and may have empty storage settings. File operations, storage capacity, and file-size limits depend on permissions, plan limits, and deployment configuration. Google Sign-In and Google Workspace transactional email may involve processing limited personal data outside Türkiye. Backups may also be stored, when needed, on company-owned servers located in Türkiye and using encrypted disks.
Production database backups are created weekly, retained for 30 days, and, under ordinary conditions, deleted on a rolling basis after that period.
TWS keeps collaboration activity attached to the related resource. Supported communication features include Card comments, Board announcements, announcement comments, and emoji reactions on supported resources.
Notifications may be generated for events such as invitations, connection requests, assignments, comments, announcements, reactions, and approval workflow activity. Notification behavior may change as the product evolves.
Where enabled by the applicable subscription plan, deployment, and user permissions, users may publish selected static web files or Card content publicly. Public Card Trees may expose a Card and eligible descendants according to their share scope and publication settings.
Public publishing is not available in every plan or deployment. Users are responsible for content they choose to publish publicly.
TWS provides a sanitized database download and supported folder downloads for data that a user is authorized to access. Depending on the export scope, an export may include Board content and information entered by or relating to other Board members. Folder downloads may contain compressed archives of uploaded files. Exported data is no longer protected by TWS controls after download.
Export availability and contents depend on the user’s permissions, the selected export operation, and the deployment configuration. Exporting data does not grant access beyond the permissions already available to the user.
Users should avoid placing personal information in shared Board content unless it is appropriate for that Board and its members.
TWS exposes authenticated HTTP endpoints used by the web application and supported integrations. API access is subject to authentication, permissions, plan limits, availability, and the endpoint capabilities provided by the deployment.
TWS may provide free and paid plans. Plan configuration may control Board limits, member limits, storage capacity, file-size limits, and features such as form design, Templates, notifications, static website publishing, and public Card Tree publishing.
The availability of paid subscriptions, payment processing, upgrades, renewals, and billing management depends on the product release and deployment. These matters are governed separately by the applicable Subscription and Billing Terms when available.
TWS is actively developed. Features, limits, supported integrations, and deployment options may be expanded, modified, replaced, or discontinued. Where reasonably possible, changes will preserve compatibility with existing user data and established workflows.
The features described in this specification represent intended product design and supported behavior of TWS. TWS is software under active development and is not guaranteed to operate without errors, interruptions, or unexpected behavior. A feature marked as available may still depend on permissions, plan limits, provider availability, or deployment configuration.
Actual behavior may differ from this specification due to software defects, configuration, permissions, subscription limits, external services, network conditions, maintenance, browser behavior, or other technical factors.
This specification describes intended capabilities and does not constitute a guarantee that every feature will always be available or operate in every situation.
This specification is informational and does not by itself create a service promise, warranty, or contractual commitment.