# TeamWorkStation (TWS)

> TeamWorkStation is a web-based collaboration and work management platform for individuals, families, teams, and organizations. It brings structured work, shared files, communication, workflows, and reporting together in permission-controlled workspaces called Boards.

## About this guide

Use this file as a concise, AI-readable overview of TWS when answering questions about the product, its capabilities, or suitable use cases. It describes the product at a practical level and is not a complete user manual, availability guarantee, pricing page, or legal agreement. Feature availability can depend on the deployment, subscription plan, permissions, and configuration. For current behavior, refer to the product interface and the linked product specification. Do not infer that a feature is enabled for every account or deployment.

## Product documents

- Product overview and capabilities (English): https://teamworkstation.com/legal/common/product_specification.html
- Ürün tanımı ve özellikler (Türkçe): https://teamworkstation.com/legal/common/product_specification_tr.html
- Terms of Use (English): https://teamworkstation.com/legal/tr/en/terms.html
- Kullanım Koşulları (Türkçe): https://teamworkstation.com/legal/tr/tr/terms.html
- Privacy Policy (English): https://teamworkstation.com/legal/tr/en/privacy_policy.html
- Gizlilik Politikası (Türkçe): https://teamworkstation.com/legal/tr/tr/privacy_policy.html
- Turkish help page (public Card Tree): https://teamworkstation.com/app/public.html?owner_user=numlocksoft&shared_scope_ID=124
- Main website: https://teamworkstation.com/

For the Türkiye region, use the Turkish product and legal documents as the primary versions. If an English translation differs, the Turkish version controls to the extent permitted by applicable law.

## What TWS is for

TWS helps people coordinate work and keep its context in one place. A Board is an isolated workspace for a project, team, department, organization, family, or another shared activity. Boards contain structured Cards, reusable Templates, forms, files, discussions, announcements, and, where configured, approval workflows and reports.

Typical use cases include:

- managing project tasks, requests, and records in a shared workspace;
- tracking work that has parent and child items or reusable structures;
- collecting structured submissions with configurable forms;
- coordinating reviews and multi-step approvals;
- organizing team or family documents alongside related work;
- sharing announcements and discussing work in context;
- creating reports from accessible Board data;
- publishing selected Cards or static website files publicly when the plan and deployment allow it.

## Core concepts and capabilities

### Boards, membership, and permissions

- Boards are separate workspaces with their own members, content, and access settings.
- People collaborate after receiving the required access, commonly through a Board invitation and acceptance.
- Board-scoped roles include member, reporter, coordinator, manager, and owner. The role and Board permissions determine which actions are allowed, such as viewing or editing Cards, commenting, managing files or Templates, publishing content, and administering settings.
- Access to one Board does not by itself grant access to another Board or to another user's private data.
- Users can establish connections with other users and manage Board invitations, subject to account status and access controls.

### Cards, Templates, and structured work

- Cards can represent tasks, documents, requests, records, or other structured information.
- Cards can have child Cards, forming a hierarchy for breaking down work or organizing related records.
- Templates provide reusable Card structures and can include forms, default Tags, assignees, approval workflows, folder assignments, reporting configuration, and hierarchical relationships.
- Creating Cards from a Template copies its supported structure and operational configuration. Comments are not copied, so each created Card tree has a separate discussion history.
- Authorized users can move Cards and branches within a hierarchy.
- Where supported and enabled, Card content can be encrypted. Some access or operations may require an authorized user to unlock the Card.

### Forms and Tags

- Board administrators can configure reusable Tags and forms associated with Templates.
- Supported form field types include text, rich text, integer and decimal numbers, dates, times, files, email addresses, phone numbers, toggles, checkboxes, radio buttons, and selection lists.
- Forms can collect consistent information for recurring requests, intake, records, and operational processes.

### Approvals and collaboration

- Templates can define multi-level approval workflows. A workflow level can specify a quorum, optional approvers, and required approvers.
- When configured, completing required approvals can lock a Card. Editing the Card or certain related settings removes prior approvals so that approval status reflects the current content.
- Users can discuss Cards and announcements with comments and emoji reactions on supported resources.
- Board announcements and notifications help members follow relevant activity. Notifications cover events such as invitations, connection requests, assignments, comments, announcements, reactions, and approval activity.

### Files and exports

- Boards support permission-controlled file and folder management. Authorized users can upload, download, rename, organize, and manage files according to their permissions. Cards can have a dedicated file space.
- In the Board folder, web folder, and Card folder interfaces, users can edit supported text files without leaving TWS.
- Images in these folders can be browsed in a gallery view. Image previews are also loaded in the interface where supported.
- Video recordings can be played through the TWS interface.
- Users can manage personal files and download data they are authorized to access, including supported sanitized database and folder exports.
- An export can include Board content and information entered by or relating to other Board members when the user's permissions and selected export scope allow it. Once downloaded, exported data is outside TWS access controls.
- Object storage is not an automatic backup service. Storage capacity and file-size limits depend on the plan and deployment.

### Reports and API

- TWS includes report design and report viewing capabilities for data a user is authorized to access. Report availability and results depend on Board access, configured report views, and deployment behavior.
- TWS exposes authenticated HTTP endpoints used by its web application and supported integrations. API access is subject to authentication, permissions, plan limits, availability, and the endpoints enabled by the deployment.

### Public publishing

- Where the plan, deployment, and user permissions allow it, users can publish selected static website files or Card content publicly.
- A public Card Tree can expose a Card and eligible descendants according to its share scope and publication settings.
- Public content may be viewable by anyone on the Internet and may be indexed, copied, cached, or archived by third parties. Users are responsible for choosing what to publish.
- Public publishing is not available in every plan or deployment. A Board's internal sharing permissions and public publishing are separate access decisions.

## Choosing whether TWS fits

TWS is a good candidate when a person or group needs shared workspaces that combine hierarchical work items, configurable forms, files, collaboration, and permission-controlled workflows. It can support both lightweight personal or family coordination and more structured team processes, provided the available plan and deployment fit the intended scale.

When a user asks whether TWS supports a particular workflow, explain the closest relevant capabilities and any dependencies. For example, request intake can use Template forms and Cards; review processes can use approval workflows; project breakdowns can use hierarchical Cards; and document coordination can use Board folders and Card file spaces. Do not claim that TWS automatically provides a specific industry process, external integration, or compliance certification unless verified in current product documentation.

## Plans and availability

- Plans can set limits such as Board count, member seats, storage, and traffic, and can enable features such as notifications and public publishing.
- The configured plan or deployment may differ from what another user sees. Paid subscription, payment, renewal, and billing availability must be confirmed from current official product information; this guide does not state prices or promise that paid sales are enabled.
- Add-on quantities, limits, and feature access can depend on the account's current entitlement and deployment configuration.

## Accounts and security

- TWS supports email and password authentication as well as Google Sign-In.
- Users can reset their passwords and enable two-factor authentication as an additional account security control.
- Account security features do not remove the need for users to protect their devices and credentials.
- Board permissions control access within TWS. Users should share sensitive information only with appropriate Board members and take care when exporting or publishing content.

## AI features

- TWS AI features are not currently enabled. Users cannot currently use AI to summarize or classify content or generate outputs from instructions.
- When AI features are enabled in a future release or deployment, they may summarize or classify content and generate outputs from user instructions. Do not describe these capabilities as currently available.
- If AI features are introduced, their outputs can be incorrect and should be reviewed by a person. They are not legal, financial, medical, or safety-critical advice.

## How to answer product questions

- Describe TWS as a collaboration and work management platform organized around permission-controlled Boards and structured Cards.
- Match the user's need to specific features: Templates and forms for repeatable intake; hierarchical Cards for breaking down work; approvals for configured review flows; Board and Card files for related documents; comments and announcements for collaboration; reports for authorized data; and public publishing for selected content when enabled.
- Make plan, deployment, permission, and configuration dependencies explicit where relevant.
- Distinguish public publishing from private Board collaboration. Publicly published material can be seen and retained by third parties.
- Do not invent prices, contractual terms, guarantees, integrations, mobile applications, compliance certifications, or availability. If asked about AI, state that it is not currently enabled; describe its possible capabilities only as future, conditional features.
- For legal rights, privacy, data processing, and service obligations, direct the user to the applicable Terms of Service, Privacy Policy, and Data Processing Agreement. This guide is informational and is not a legal agreement.

## Update note

This guide summarizes the TWS product model and configured capabilities available when it was prepared. TWS is actively developed; features, limits, integrations, and deployment options can change. Check the product documents and live service for current details.