See what Arkonkt can do and how its main areas work together.

What Arkonkt is

Arkonkt is a workspace app for organizing work, information, communication, planning, people, time, and AI support.

It is designed to stay close to daily work rather than replace every tool around it. On desktop, Arkonkt can sit at the side of the screen while the user continues working in documents, email, websites, customer systems, or other programs.

The value of Arkonkt comes from connection. A Task is more useful when it is connected to the Project it belongs to. A Project becomes more understandable when it contains Notes, Communications, time, and decisions. Review becomes more valuable when the workspace has enough real activity to reveal workload, delivery signals, and progress.

Arkonkt can support a company, a team, a private user, or a family. The structure stays familiar while each workspace keeps its own purpose, people, information, and boundaries.

Practical example

A small business can use one workspace for the company, Projects for customers, Tasks for delivery work, Notes for decisions, Communications for customer contact, Time Tracking for actual effort, Resources for planning, and Review for understanding what needs attention.

Workspaces, roles, privacy, and visibility

A workspace is the boundary that keeps related information together. A business workspace can contain company work and team members. A private workspace can contain personal Tasks and Notes. A family workspace can contain shared responsibilities, plans, and events.

People only see the workspaces they belong to. Joining one workspace does not give access to another. This allows a user to keep business, private, family, customer, or project contexts separate while using the same app.

Every shared workspace has an owner. The owner manages protected workspace actions such as membership, important settings, ownership, archive or delete actions, approvals, and selected tool controls. Members contribute to the work available to them without controlling the whole workspace.

Inside a workspace, some information can still be private. A user can prepare a private Task or Note, then change it to shared when the team should see, discuss, or act on it.

Workspace boundaries also apply to AI, notifications, search, references, and published knowledge. Arkonkt should use only information available to the user in the active context.

Practical example

A consultant can keep customer work in a business workspace and personal planning in a private workspace. A colleague invited to the business workspace can help with shared Tasks without seeing private Notes or the user’s private workspace.

Projects, Epics, Tasks, and ToDos

Arkonkt supports both structured delivery and quick daily follow-up.

A Project is a flexible work area. It can represent a traditional project, but it can also represent a customer, service job, client case, internal activity, delivery, study plan, family plan, or personal goal.

A Task is a normal work item that needs progress, responsibility, planning, follow-up, or completion. A Task can belong directly to a Project, remain outside a Project, or sit under an Epic.

An Epic groups several related Tasks under one larger objective. It helps users understand the bigger piece of work without losing the individual actions needed to complete it.

A ToDo is smaller and more personal. It is useful for reminders and simple follow-up. ToDos do not sit inside Epics, which keeps them lightweight.

Projects, Epics, Tasks, and ToDos can receive clear workspace-based keys such as AS-3, making work easier to identify, discuss, and search for without changing normal permission rules.

Capability model

Workspace
├── Project
│   ├── Task
│   └── Epic
│       └── Task
├── Task
├── Epic
│   └── Task
└── ToDo

Practical example

A customer onboarding process can be represented as a Project. An Epic can represent “Complete onboarding,” with Tasks for the first meeting, data collection, setup, training, and follow-up. A personal ToDo can remind one team member to confirm a small detail.

Notes and connected knowledge

Notes keep the information behind the work: meeting points, decisions, ideas, instructions, customer context, research, plans, and knowledge that should not disappear.

Notes can be private or shared. Private Notes support personal preparation and drafting. Shared Notes help the workspace build a useful history and reduce repeated questions.

Sections, tags, pinning, archive behavior, logs, and templates make Notes useful as the workspace grows. A team can create reusable templates for customer meetings, weekly reviews, project updates, interviews, decisions, or service reports.

Notes connect naturally to action. A meeting Note can produce Tasks. A customer Note can explain why a Task exists. A long Note can be summarized or reviewed with AI. A reusable Note template can be created or revised with AI while the user remains responsible for applying and saving the result.

The Notes Focus experience gives desktop users a larger writing space when the compact side layout is not enough.

Practical example

After a customer meeting, a shared Note records the request, the agreed decision, and the next steps. Two action points become Tasks, while the Note remains available as the background for the team.

Communications, calendars, availability, and team chat

Important work often begins in communication. Arkonkt connects messages and meetings with the Tasks, Notes, Projects, and follow-up they create.

Connected email and a user’s personal calendar belong to that user account. They can support the user across workspaces without becoming shared workspace data automatically.

The shared calendar belongs to the workspace. It can show shared meetings, events, and confirmed bookings that workspace members need to understand together.

Availability lets a user publish bookable time slots. Customers, patients, partners, or other people can choose a suitable time from the slots made available. Confirmed bookings can appear in the shared calendar, helping the workspace respond even if the original member becomes unavailable.

Team chat keeps quick discussion visible to the workspace instead of hiding important knowledge inside private member-to-member messages. @ mentions can draw a member’s attention, while / references can connect a discussion to a Task, Epic, or Note.

The goal is not to keep every message forever. The goal is to turn useful communication into clear work, decisions, and follow-up.

Practical example

A customer email creates a Task connected to the customer Project. A meeting is booked through availability, appears in the shared calendar, and produces a Note and follow-up Tasks after the discussion.

Projects, Resources, Time Tracking, and actual effort

Projects explain what the work belongs to. Resources explain what is available to deliver it. Time Tracking explains how much effort the work actually required.

Project planning can include expected values such as hours, capacity, teams, external resources, assets, and cost-related information. This helps owners describe what they believe the work will need.

Resources can represent people capacity, teams, external support, equipment, rooms, vehicles, tools, or other practical assets. Utilization helps show whether the plan is balanced or whether people and assets are overloaded or underused.

Time Tracking lets members register working hours and connect them to the right Project, customer, job, or activity. Monthly reports can be reviewed, returned for correction, and approved by the owner.

Approved time becomes trusted actual information. It can be compared with planned values to reveal whether a customer, Project, or service required more or less effort than expected.

This connection helps owners improve planning, pricing, workload decisions, staffing, and delivery expectations.

Practical example

A Project is planned for 20 hours. Members later report 35 approved hours against it. Arkonkt helps the owner see that the real effort exceeded the plan and decide whether pricing, capacity, or future delivery assumptions need to change.

Review, workload, milestones, and delivery visibility

Review gives a wider view of the active workspace. It becomes more useful as the workspace gains real Tasks, Projects, members, dates, milestones, and approved activity.

Review can help answer practical questions:

• What needs attention now?
• Is work moving forward?
• Are overdue or due-soon items increasing?
• Is new work being created faster than work is completed?
• Who has too much open work?
• Which milestones or deliveries may be at risk?
• Where does the team need support?

Charts and compact summaries make it easier to understand patterns that are difficult to see in a normal list. Review can show status mixes, created-versus-completed trends, open work by assignee, completion activity, milestones, and wider delivery signals.

Review is not intended to judge people. It is intended to help owners and members understand the situation, remove blockers, balance workload, and make better decisions.

Practical example

Review shows that one team member has many open Tasks and one milestone is approaching with several items still blocked. The owner can redistribute work and address the blocker before the delivery date is missed.

AI & Tools

AI & Tools is a collection of focused assistants rather than one chatbot trying to handle everything.

Depending on what is enabled and available, the toolbox can include:

• Workspace AI Assistant
• Meeting Assistant
• Document OCR Assistant
• Invoice Assistant
• Expense Assistant
• Local Transcription Assistant
• Email Drafting Assistant
• Recruitment Workflow
• Job Posting Generator
• Candidate-to-Position Matching
• Knowledge Agent
• Daily Brief

The Workspace AI Assistant can answer questions about visible information in the active workspace. A user can focus a question on a specific Task, ToDo, Epic, or Note.

Meeting tools can help turn meeting information into summaries, decisions, Notes, and proposed Tasks. OCR can extract text from documents and images. Local transcription can turn audio into text on the device. Email drafting can use selected workspace context to prepare a message.

Invoice, expense, and hiring tools support more specialized workflows. These areas may contain sensitive information, so results must be reviewed carefully and access must follow workspace roles and visibility.

AI supports the user; it does not replace the user. Important results should be reviewed before they are saved, sent, approved, published, or turned into work. Confirm-before-create behavior keeps the user in control.

Practical example

A meeting transcript is summarized. The assistant identifies three possible follow-up actions, but the user reviews them and confirms only two as Tasks.

Local AI, cloud AI, and privacy choices

Arkonkt can support both local AI and cloud AI where the necessary setup is available.

Local AI runs on the user’s own computer. It can be useful when sensitive information should stay on the device, but it depends on the computer’s hardware, installed models, and local AI health.

Cloud AI uses an external provider. It can offer stronger support for complex writing, analysis, or reasoning and may be easier to use on a device that cannot run a suitable local model. It depends on internet availability, service availability, and account or subscription conditions.

Some extraction steps are designed to work locally, including OCR, transcription, invoice extraction, and receipt extraction. A user can review the extracted information manually or choose AI refinement according to the configured provider.

Privacy decisions should match the work. Sensitive internal information may be better suited to local processing. More complex tasks may benefit from cloud AI when it is appropriate to send selected context.

Workspace boundaries still apply. AI should use only information available to the user in the active workspace and should not expose private or unrelated data.

Practical example

A user extracts text from a confidential document locally, reviews it, and uses local AI to summarize it. For a complex public marketing draft, the same user may choose cloud AI.

Knowledge Agent and controlled external knowledge

Knowledge Agent lets a workspace owner publish selected knowledge for people outside the workspace.

This is useful when customers, partners, another team, or external users need answers but should not receive access to the full workspace.

The owner controls what information is published. External users receive answers based on that approved knowledge rather than on every Task, Note, file, or private workspace detail.

Knowledge Agent can support product guidance, service information, procedures, partner documentation, customer support, or other controlled knowledge-sharing needs.

Because published knowledge crosses the workspace boundary, the owner should review what is included, who can access it, what disclaimers apply, and whether the information is still current.

Practical example

A service company publishes approved support documents through Knowledge Agent. Customers can ask common questions without joining the workspace or seeing internal Tasks, Notes, customer records, or team discussions.

Local, connected, and offline-first use

Arkonkt is designed offline-first. Local work should remain available when the network is weak, the backend is temporarily unavailable, or a signed-in session cannot be refreshed immediately.

Connected workspaces can sync when service is available. Local changes can be stored on the device and synchronized conservatively rather than forcing the user to stop working.

Signing in does not automatically upload, merge, move, or delete local workspace data. Moving local data into a connected context must be an explicit action.

Some operations still require a connection. Account creation, membership, cloud AI, shared publishing, approvals, and destructive workspace actions may need online verification.

The important principle is continuity: ordinary work should continue locally, while connected features resume safely when the service returns.

Practical example

A user updates Tasks and writes Notes while travelling without a stable connection. The local work remains available, and connected changes synchronize later when the service is restored.

Practical ways to use Arkonkt

Arkonkt is flexible because the same connected structure can support different kinds of users.

Small business

A business workspace can use Projects for customers, Tasks for delivery, Notes for decisions, Communications for customer contact, Time Tracking for actual effort, Resources for capacity, and Review for workload and delivery visibility.

Consultant or freelancer

A consultant can use one Project per customer, connect emails and meetings to Tasks and Notes, record time against each customer, and compare real effort with expectations.

Service business

A service company can use Projects for jobs or cases, availability for customer bookings, the shared calendar for team awareness, Resources for vehicles or equipment, and Time Tracking for actual delivery effort.

Team

A team can use Epics to group larger objectives, Tasks for individual work, Notes for shared context, team chat for quick discussion, milestones for delivery dates, and Review for progress and workload.

Private user

A private workspace can organize daily Tasks, personal ToDos, Notes, study plans, home Projects, documents, reminders, and AI support without mixing that information into a business workspace.

Family

A family workspace can combine shared Tasks, Notes, Projects, calendar events, responsibilities, and plans while each person still keeps unrelated private information outside the workspace.

The goal is not to enable every feature immediately. Arkonkt becomes more useful as the parts that matter to the user begin to connect.