Glossary

The rules that define how Docyrus may and may not be used.

The rules and mechanisms that control who can access data, apps, agents, workflows, actions, or resources.

A user or customer-level access record used to sign in, manage settings, and use Docyrus services.

Data related to a customer account, users, billing, configuration, subscriptions, settings, and service usage.

The customer-facing area for managing account settings, usage, billing, resources, users, and service configuration.

A permission layer that defines which users, roles, or teams can view, edit, or act on records, fields, or resources.

A step that performs an operation, such as sending a message, updating a record, calling an API, or running an agent.

A specific action step inside a visual or structured workflow.

Permission control that determines who can perform a specific action, such as approve, publish, export, delete, or run.

A record of user, app, agent, workflow, or system activity in Docyrus.

A structured card format used to display interactive content or actions across supported apps, workflows, or communication channels.

An extension that brings Docyrus functionality into another product or interface.

An additional paid feature, service, resource, or capacity added to an active Docyrus plan.

A user with management permissions over users, roles, apps, agents, data models, integrations, resources, and security settings in a tenant.

A configurable AI-assisted digital work component in Docyrus that can use context, follow instructions, call tools, trigger workflows, and produce outputs.

Memory used by an agent to improve continuity, personalization, or task performance within the customer's configuration.

The coordination of agent steps, tools, sub-agents, workflows, approvals, and outputs.

The execution layer where agents process context, follow instructions, call tools, and produce responses or actions.

A specific capability, instruction set, or reusable behavior that helps an agent perform a defined task.

A controlled tool that an agent can call to read data, update records, run actions, query systems, or interact with external services.

The Docyrus development environment where users build apps, agents, data models, workflows, integrations, and platform components with AI-assisted and agentic tools.

An agent that uses AI models to interpret context, generate outputs, call approved tools, and assist with tasks or workflows.

The Docyrus builder for creating agents with instructions, tools, knowledge, memory, guardrails, approvals, and deployment options.

The usage unit Docyrus uses to measure AI operations such as model calls, agent work, embeddings, retrieval, tool calls, and AI processing.

The number of AI credits used by a model request, agent run, workflow, retrieval step, embedding operation, or other AI action.

Storage used for indexes that support AI retrieval, embeddings, semantic search, and RAG.

The Docyrus builder for creating mobile app experiences that use shared data, workflows, native mobile capabilities, and AI interactions.

A broad category of machine learning model used for language, image, embedding, speech, ranking, reasoning, analysis, or other AI tasks. Examples include GPT, Claude, Gemini, Llama, Mistral, DeepSeek, Command, embedding models, image models, and speech models.

A product or system designed with AI as a core layer from the start, not added later as a separate feature.

The result generated by an AI model, AI service, agent, or AI-assisted workflow.

The Docyrus builder for creating portals with branded access, permissions, data sharing, forms, pages, and embedded AI experiences.

Docyrus services related to agents, LLM access, content generation, analysis, summarization, embeddings, RAG, vector search, and AI-assisted workflows.

The Docyrus area for building and modifying agents. Users can manage agent preferences, LLM selections and settings, instructions and output behavior, agent tools, capabilities, data sources, memory and context, skills, plugins, knowledge base, prompts, and help settings in this section.

The Docyrus builder for creating web apps with data models, pages, workflows, permissions, and AI-assisted features.

A data source designed for reporting, analysis, aggregation, or analytical workloads.

Storage used for analytical workloads, reporting, aggregation, and advanced data analysis.

A client used by code or tools to call Docyrus APIs.

A specific API address that receives requests and returns responses for a defined function.

A secret credential used to authenticate access to an API or third-party service.

A request sent to an API endpoint.

A business application built, installed, customized, published, or used on the Docyrus Platform.

The collection of ready-made apps that users can discover, install, and adapt inside Docyrus.

A ready-made starting point for building or installing an app on Docyrus.

A required confirmation from an authorized person before a step or action continues.

A workflow that pauses an action until an authorized person reviews and approves it.

A native Docyrus agent focused on app architecture, data structures, and no-code building blocks. Archy works like a coding agent but focuses more on system structure, data models, and reusable no-code components.

A conversational AI experience that helps users complete tasks, find answers, generate content, or work with data.

A file attached to a record, message, form, workflow, app, or document.

A log of security-relevant or operational actions, such as access, changes, approvals, and administrative activity.

A traceable record of important actions, changes, approvals, access events, or security-relevant activity.

The process of confirming who a user, app, service, or system is.

The process of deciding what an authenticated user, app, service, or system can access or do.

A user who has been granted access to specific Docyrus features, apps, agents, data, or workflows.

A configured process that performs actions automatically based on triggers, schedules, rules, or events.

A single execution of an automation or workflow.

A service that runs tasks, jobs, workflows, or automations in the background without direct user interaction.

A technical copy of data used to support recovery, continuity, or system protection.

The period used to calculate subscription fees, resource usage, overage, and other billable items.

A record used to calculate or verify charges, subscriptions, usage, overage, taxes, and payments.

Workflow logic that sends different cases through different paths based on rules or conditions.

The use of customer or product identity elements such as name, logo, colors, tone, and visual style.

A configuration model where a customer connects or uses their own database with Docyrus, subject to supported architecture, security, and plan terms.

The environment where authorized users create, configure, test, and prepare apps, agents, portals, data models, and workflows.

A reusable platform capability such as data infrastructure, auth, workflows, integrations, deployment, security, or agent framework.

A configuration option that lets a customer connect their own provider API key to use supported third-party AI or service providers through Docyrus.

A customer data platform app or category that centralizes customer records from multiple sources into a unified profile.

A conversational interface that can answer questions, collect information, route requests, or trigger workflows. Chatbots can be embedded into websites or apps, or connected to messaging channels such as WhatsApp.

A browser extension that gives users quick access to Docyrus tools, agents, and platform actions from Chrome. It can also let agents see and work with the current web page when permitted by the user and browser context.

A command-line tool used to operate, inspect, configure, or automate Docyrus from a terminal.

An OAuth method used for server-to-server authentication without direct user interaction.

A reusable software library that helps developers connect to Docyrus APIs or services.

A native Docyrus coding-focused agent for building, shaping, and refining software, screens, apps, and internal tool experiences.

An additional commercial document that defines special pricing, service terms, resource limits, or customer-specific conditions.

The process of meeting applicable legal, contractual, security, privacy, or industry requirements.

A reusable set of UI components used to build consistent forms, tables, pages, charts, navigation, and app experiences.

Processing capacity used to run apps, agents, workflows, queries, integrations, and AI-related tasks.

A technical limit on how many processes, requests, jobs, or actions can run at the same time.

A rule that determines whether a workflow follows one path or another.

Non-public business, technical, commercial, security, customer, product, or financial information shared between the parties.

An external account connected to Docyrus for integration, data access, automation, or AI tool use.

A reusable connection that links Docyrus with an external app, service, database, file system, API, or platform.

A report that shows how resources, credits, requests, runs, or other usage units were consumed.

The process of reducing or summarizing long context so an AI model can continue working within technical limits.

A secret, token, key, password, certificate, or similar item used to authenticate access.

The assignment of AI credit capacity to a tenant, user, team, app, agent, or workflow.

The remaining amount of AI credits available for use in a billing period or package.

The multiplier or calculation factor used to convert different model or AI operations into AI credit consumption.

An agent created or configured for a specific customer workflow, task, department, or business process.

Paid development work created for a customer's specific requirements outside standard platform functionality.

A customer-owned domain connected to a Docyrus app, portal, or published experience.

Customer-defined instructions that shape how an agent, assistant, app, or workflow behaves in a specific context.

A customer-specific connection built between Docyrus and another system, service, database, or API.

A customer-defined query used to retrieve, transform, filter, or calculate data beyond standard views or filters.

The company, institution, or person that subscribes to or uses Docyrus services under an agreement or order form.

Content entered, uploaded, created, or configured by the customer, including files, prompts, templates, outputs, reports, rules, and documents.

All data uploaded, created, processed, stored, accessed, or transferred by the customer or authorized users through Docyrus.

A named Docyrus success contact who helps with onboarding, adoption, reviews, escalation, and ongoing customer success.

A visual workspace that shows metrics, charts, reports, tasks, alerts, or operational views.

The connection between UI components, forms, views, or workflows and live Docyrus data.

The process of deleting customer data from active systems, subject to legal, billing, security, and backup retention requirements.

The process of downloading or transferring customer data from Docyrus in supported formats.

The structured design of data sources, fields, relationships, permissions, and business logic.

A legal addendum that defines data processing roles, obligations, safeguards, and privacy terms between the customer and Docyrus.

The location or region where data is stored or processed, subject to the applicable plan or agreement.

The period and rules for keeping data in active systems, backups, logs, billing records, or legal records.

A structured source of data used by Docyrus apps, agents, reports, workflows, APIs, and queries.

A configured connection between Docyrus and a database.

The amount of database capacity used by records, data sources, operational data, and app data in Docyrus.

A support model where a customer receives named success or account guidance as part of the purchased support plan.

The process of making an app, agent, portal, workflow, or service available in a target environment.

A structured set of visual rules, UI components, patterns, and standards used to build consistent products.

An OAuth flow that lets users authorize a device or CLI by entering a code in a browser.

A structured or unstructured file or content item used for records, knowledge, templates, analysis, or workflows.

A native Docyrus agent that helps users ask questions, explore records, add data, generate reports, and understand business data.

The Docyrus component and interface system for building consistent web and mobile app experiences.

The Docyrus data source foundation for managing structured records, fields, relationships, queries, and data access.

The Docyrus command-line tool for authentication, tenant switching, schema management, API calls, and developer operations.

A native desktop application that provides access to selected Docyrus capabilities outside the browser, including using apps, Docy, Cody, Opsy, and Studio. Cody can also be used locally where supported.

The Docyrus business platform for building, running, and publishing apps, agents, portals, workflows, data models, integrations, and AI-assisted business systems.

A working version that has not yet been published or released.

A Docyrus query builder used to create, test, and manage queries over data sources.

A Docyrus query language or query layer used to work with structured platform data.

A special AI context management strategy where an agent can receive different context in different cases. In Docyrus, the agent builder can define this dynamic context structure based on use case, user role, data source, workflow state, or task type.

A hook that triggers actions, automations, parsing, or routing based on incoming or outgoing email events.

A reusable email structure used by apps, workflows, automations, or agents to generate consistent messages.

A numeric representation of text, files, records, or other content used for semantic search and AI retrieval.

Encryption applied to data while it is stored.

Encryption applied to data while it moves between systems, users, services, or networks.

A person who uses an app, portal, agent, workflow, or other experience built or published through Docyrus.

A specific API address or service address that receives requests.

Advanced services for enterprise customers, such as custom SLAs, private cloud, on-premises deployment, advanced audit logs, data residency, and special security terms.

A separated area such as preview or production where apps, agents, workflows, and services run.

A trigger that starts when a defined event occurs.

A Docyrus add-in for working with Docyrus data, reports, queries, and AI-assisted spreadsheet tasks inside Microsoft Excel.

A standalone frontend developed and served independently with any software language or framework, while using Docyrus as the backend, data, workflow, permission, or AI layer.

A data source connected from an external system, database, file, API, or third-party service.

Usage rules designed to protect platform stability, cost balance, service quality, and other customers' access.

A defined data attribute inside a record, such as name, status, date, amount, owner, or category.

Permission control that determines who can view or edit specific fields inside a record.

A digital file uploaded, stored, processed, linked, generated, or used through Docyrus.

The processing of files for extraction, indexing, AI analysis, conversion, validation, preview, or workflow use.

The amount of storage used by uploaded, generated, attached, or managed files.

The process of adapting an existing AI model with additional data for a narrower use case or behavior.

Content created by AI services, agents, workflows, or platform functions, such as text, summaries, reports, code, images, or analysis.

A version-controlled code repository used to store, track, and manage source code.

The rules, controls, permissions, approvals, logs, and policies used to manage safe and accountable platform use.

Rules and controls that limit what an agent, workflow, or AI service can access, produce, or do.

A native Docyrus guidance agent that helps users with onboarding, product navigation, setup steps, and recommended next actions.

An architecture where backend services, data, APIs, workflows, and logic can operate independently from a fixed user interface.

AI use that may affect legal, financial, medical, employment, public safety, rights-related, or similarly sensitive decisions.

HTML-based content created, edited, stored, or published through Docyrus.

A manual review step used to check AI outputs, workflow decisions, data changes, or actions before they continue.

A control model where a person reviews, approves, corrects, or supervises AI or automation before a sensitive action is completed.

The computing, storage, database, networking, AI, runtime, security, and platform resources used to run Docyrus services.

The amount of infrastructure resources consumed by apps, agents, workflows, users, integrations, data, and AI services.

A pricing model where customers pay mainly for consumed resources such as storage, AI credits, automations, API requests, and integrations.

An app experience embedded inside another Docyrus app, page, record, or workflow context.

Directives that tell an agent, assistant, workflow, or AI service how to behave or complete a task.

A connection or workflow between Docyrus and another system that allows data, actions, or events to move between them.

A request made between Docyrus and an external system through an integration, connector, API, webhook, or MCP tool.

A request sent through an integration or connector between Docyrus and another system.

An app that is accessed through the Docyrus Platform frontend and used by internal users or authorized teams.

A data source managed inside Docyrus.

A schema format used to define, validate, and document the structure of JSON data.

A query and transformation language used to extract, transform, or calculate values from JSON data.

A collection of documents, data, policies, FAQs, or reference materials that agents or users can search and use.

A type of AI model focused on language, reasoning, conversation, text generation, summarization, and tool use. LLM families include GPT, Claude, Gemini, Llama, Mistral, DeepSeek, and Command.

A service model where Docyrus or an authorized party operates, manages, or maintains certain systems or workflows for the customer.

The Docyrus area where apps, agents, templates, or reusable assets can be discovered, installed, published, or monetized.

A protocol used to connect AI systems with tools, data sources, services, and external systems in a structured way.

A configured connection that lets Docyrus or an agent interact with tools, systems, or data sources through MCP or a similar standard.

A governed gateway that routes, scopes, logs, and controls MCP-based tool or data access.

A tool used to inspect, test, debug, or understand MCP servers, tools, schemas, and responses.

A server that exposes tools, data, or services to compatible AI systems through MCP.

Stored context that helps an agent or assistant remember relevant preferences, facts, or prior interactions within allowed settings.

Technical information about usage, events, actions, timestamps, errors, performance, and system behavior, excluding the substance of customer data.

A security method that requires more than one factor to verify user identity.

The process of moving data, content, configuration, or workflows from another system into Docyrus.

A mobile application or mobile experience built, published, or accessed through Docyrus.

A mobile client used to access Docyrus apps, agents, workflows, notifications, or platform features.

The ability to work with different model providers or model types instead of depending on a single AI provider.

The raw or processed result returned by an AI model after receiving input.

A company, service, or ecosystem that provides AI models used by Docyrus or connected by the customer. Examples include closed model providers such as OpenAI, Anthropic, Google, Microsoft, and xAI, and open model ecosystems or providers such as Meta, Mistral, DeepSeek, Cohere, and Hugging Face.

The process of sending an AI request to a selected model or provider based on configuration, availability, cost, or task type.

The process of choosing which AI model will be used for a task, agent, workflow, or request.

The process of using data to train or improve an AI model's general behavior or capabilities.

The category or function of an AI model, such as language, embedding, image, speech, or reasoning.

The specific release or version of an AI model used for a request, workflow, agent, or service.

A group of agents that work together, often with a supervisor agent delegating tasks to specialized agents.

An agent built into the Docyrus platform experience, such as Docy, Cody, Archy, Opsy, or Guidy.

Credits that cannot be carried into another period, transferred to another account, refunded, or converted into cash.

An authorization connection that lets Docyrus access a third-party service with user or admin permission.

An authorization framework used to grant secure access to services without sharing passwords.

Storage used for files, attachments, documents, media, exports, and other object-based data.

An identity layer on top of OAuth 2.0 used for user authentication.

A deployment model where certain services are installed or operated in the customer's own infrastructure.

The setup and guidance process that helps a customer start using Docyrus correctly.

A publicly available software package that can be used, inspected, or contributed to under its license.

A machine-readable API specification that describes available endpoints, request formats, response formats, and authentication rules.

Business process data used by apps, agents, workflows, reports, dashboards, and integrations.

A native Docyrus agent that can work with local files on the user's computer, such as Excel files, images, documents, and other suitable file types, where supported.

The commercial document that defines the purchased plan, services, usage rights, prices, limits, support level, and special terms.

The company, institution, or team that owns and manages one or more Docyrus accounts or workspaces.

Usage above the included credit or resource limit.

The additional fee charged when usage exceeds an included credit or resource limit.

A specific right to view, create, edit, delete, approve, run, publish, or manage something in Docyrus.

A group of permissions that can be assigned to users, roles, teams, apps, or agents.

Any information relating to an identified or identifiable person.

An OAuth flow used to improve security for browser, mobile, or public clients.

A Docyrus service package that defines available features, resource limits, usage rights, and commercial terms.

Services that allow customers to build, run, publish, manage, and support apps, agents, portals, workflows, data, and integrations on Docyrus.

A reusable specialist agent or capability that can be used by other agents or workflows.

A Docyrus-powered access point for customers, partners, employees, suppliers, or other external or internal users with defined permissions.

A user who accesses a Docyrus-powered portal with permissions set by the customer.

A non-production environment used to test changes before they are released to users.

A reusable print or document output structure used to generate PDFs, forms, contracts, invoices, or other printable outputs.

A dedicated cloud deployment model provided for specific enterprise requirements.

The live environment where apps, agents, portals, workflows, and services are used by intended users.

Paid services such as onboarding, training, migration, consulting, custom development, custom integration, reporting, and workflow design.

The process of moving a verified draft or preview build into production.

The input, instruction, question, data, or context sent to an AI service by a user, system, workflow, or agent.

The process of improving prompts to get clearer, safer, more accurate, or more useful AI outputs.

A reusable prompt structure used to standardize AI instructions, outputs, or workflows.

A customer-owned API key or credential issued by a third-party provider and connected to Docyrus.

An app that has been deployed or made available to its intended users.

The process of making a Docyrus app, portal, page, agent, template, or workflow available to intended users.

The process of placing tasks, requests, or workflow steps in a queue before execution.

A defined allocation of capacity or usage rights.

An AI method where outputs are generated using retrieved context from customer data, knowledge bases, vector indexes, or external sources.

A technical limit on how many requests or actions can be made in a defined time period.

An access control model where permissions are assigned through roles.

A single structured data item inside a Docyrus data source, such as a customer, task, deal, ticket, or invoice.

A security model that controls access to individual records.

A defined connection between records or data sources.

A version of an app, agent, portal, workflow, template, or platform component made available for use.

A log that helps review, trace, or rerun workflow steps or automation activity.

A structured output that presents data, metrics, summaries, or analysis from Docyrus or connected systems.

A storage location for code, files, documents, templates, or reusable development assets.

A call sent to an API, service, workflow, model, or integration.

The measured use of platform resources such as storage, AI credits, automation runs, API requests, and integrations.

An add-on package that gives additional capacity such as storage, AI credits, automation runs, integration requests, or AI index storage.

The result returned after a request is processed.

The target time for Docyrus or its support team to respond to a customer support request.

An API style used to access and manage Docyrus data, resources, apps, portals, or integrations through standard web requests.

A configured connection that lets Docyrus read from or write to another system through a REST API.

The process of finding and bringing relevant information into an AI request, agent run, workflow, or answer.

A named access profile that groups permissions for users or teams.

The process of restoring a previous stable version after a release or change.

A security model that limits access to individual records or rows based on rules, roles, or tenant context.

The operating layer where apps, agents, workflows, portals, and integrations run after they are created or published.

Infrastructure and platform services required to run customer apps, agents, portals, workflows, and integrations.

A standard used for exchanging authentication and authorization data between identity providers and services.

An isolated environment for development, testing, previews, or safe experimentation.

A workflow that runs at a defined time or recurring schedule.

The structure that defines records, fields, relationships, types, validation rules, and data behavior.

A set of developer tools, libraries, or helpers used to build with Docyrus more easily.

A pricing model where fees are mainly based on the number of users or seats.

An event that may affect confidentiality, integrity, availability, access control, or platform security.

A defined set of Docyrus services, resources, support rights, and commercial conditions.

A packaged set of instructions, patterns, tools, or workflows that improves agent or developer performance for a specific area.

A service commitment that defines response times, availability targets, support scope, or other measurable service obligations.

The subscription-based right to access and use Docyrus during the agreed service period.

Human-readable code used to build software, apps, components, or integrations.

A configured limit that controls how much usage-based cost can be generated.

A commonly used term for secure certificates that help encrypt web traffic for domains and apps.

A sign-in method that lets users access Docyrus through an organization's identity provider.

A response returned in a defined format, usually JSON, so it can be validated and used by apps, agents, or workflows.

A specialized agent used by another agent to complete a narrower task.

The paid or trial-based commercial relationship that gives the customer access to Docyrus services for a defined period.

The support level purchased by or included for a customer, including support channels, response times, and service scope.

A specific level of support, such as AI support, business support, priority support, or dedicated success support.

Temporary restriction or disabling of access to a user, tenant, app, agent, integration, resource, or service.

A technical record of system events, errors, usage, actions, or platform behavior.

A higher-priority instruction that defines the behavior, role, limits, and rules of an AI assistant or agent.

A user who belongs to the customer's team and uses Docyrus for internal work, collaboration, or operations.

Documentation that explains product behavior, APIs, integrations, configuration, limits, security, or technical usage.

A reusable structure for generating or standardizing content, emails, documents, print outputs, apps, workflows, or records.

The logical Docyrus account that contains a customer's users, data, apps, agents, permissions, integrations, resources, and settings.

The ending of an agreement, subscription, service period, or usage right.

A set of visual settings such as colors, typography, spacing, and style rules used across apps or portals.

A company or service provider outside Docyrus that supplies infrastructure, models, APIs, connectors, payment, messaging, or other services.

A service not owned by Docyrus, such as a model provider, cloud provider, email service, payment service, API, or SaaS tool.

A temporary reduction in processing speed or request handling to protect stability, cost balance, or service quality.

A unit of text processed by an AI model, or a credential used for authentication, depending on context.

The amount of input and output tokens processed by an AI model during a request or workflow.

The process where an agent calls an approved tool to perform an action, fetch data, or interact with another system.

A limited period during which a customer can use certain Docyrus services under trial conditions.

An event, schedule, webhook, record change, or condition that starts a workflow or automation.

A reusable interface element such as a button, form field, table, card, modal, chart, or navigation item.

Technical and statistical data created from platform usage, resource consumption, performance, billing, security, and service operation.

A defined maximum for using a resource, service, feature, request type, or platform capability.

The process of measuring resource consumption for reporting, billing, security, and platform management.

An allocated amount of resource usage available to a tenant, user, team, app, agent, or workflow.

A person who accesses Docyrus through an account, based on permissions assigned by the customer or admin.

A resource, usage, or spending limit applied to a specific user.

Rules or checks that ensure data, inputs, forms, records, or API requests meet expected requirements.

An error returned when data, input, schema, or request format does not meet required rules.

A search method that finds semantically similar content using embeddings instead of only exact keywords.

Storage used for vector embeddings that support semantic search, similarity matching, and RAG.

A specific iteration of a platform component, app, agent, template, workflow, API, or model.

A software creation approach where users describe what they want and AI helps generate, edit, or refine working code and screens.

A no-code creation approach where users describe business logic or app structure and AI helps shape the system with reusable, tested building blocks. This can reduce AI credit consumption and make the final product safer because the system is built on tested infrastructure instead of generating every part from scratch.

A browser-based application built or published through Docyrus.

A browser-based client used to access Docyrus apps, portals, tools, or platform features.

A form built with Docyrus to collect structured data. A web form can be triggered through an API or published as a full standalone webform page.

An event-based connection that sends data or triggers actions when something happens in Docyrus or another system.

A trigger that starts when a webhook receives an event or request.

A configuration where an app, portal, or experience is presented under the customer's brand instead of the Docyrus brand.

A small embedded component that displays information, captures input, or performs an action inside an app, portal, dashboard, or page.

A Docyrus add-in for working with Docyrus content, templates, documents, and AI assistance inside Microsoft Word.

A defined sequence of steps, conditions, actions, approvals, and system interactions used to run a business process.

An automated workflow that runs steps, decisions, notifications, AI actions, or integrations based on rules or triggers.

A working area where users organize apps, agents, data, files, workflows, and projects inside Docyrus.