Frequently Asked Questions

There is no individual opt-out because WorkSights AI reads audit logs from company-owned cloud services rather than software installed on a person's device. Your organization controls who is included, which services are connected, and who can access the resulting information. WorkSights AI does not read message, email, document, or file content.

If you give members access, they can review their own activities and adjust duration estimates, which recalculates their day. Your organization decides whether individual members receive access. Access can begin with managers and expand later if that fits your policies.

No. Managers can see their own team and the people who report through that team. They cannot browse unrelated teams. Executives with organization-wide access are the exception, according to the reporting hierarchy configured by your administrators.

Yes. Each instance connects as a separate service with its own user mapping. This is the recommended setup when an organization uses multiple instances of a platform, such as multiple Atlassian Cloud instances.

Yes. You can hide scores account-wide or by user level under Settings > Account > Score Visibility. Many teams use WorkSights AI with scores disabled and rely on summaries, reports, and Observer insights instead. The Score is an optional signal, not the product.

Yes. WorkSights AI builds baselines and organizational Memory from ongoing activity. As that context grows, its reports and insights can become more specific to how your business operates. The value compounds because the historical context is retained according to your plan.

No. WorkSights AI expands what leaders can see. It identifies patterns, explains signals, and delivers insights, but people decide what action to take. The platform is designed to support judgment, not replace it.

They are indicators, not conclusions. Each insight includes its reasoning and supporting activity so a leader can review the context before acting. WorkSights AI surfaces the signal; a person verifies what it means.

You can add relevant, approved context to a user profile, such as an adjusted schedule or a period of reduced capacity. WorkSights AI uses that context when generating summaries and insights. Leaders should still review the supporting activity and speak with the people involved before drawing conclusions.

Each user has a configured work schedule. WorkSights AI estimates the time represented by activity visible across connected services and compares it with that schedule. Many teams reduce the scheduled-day baseline to allow for normal work that does not appear in a connected system.

The result is directional because it cannot measure work completed in unconnected tools or away from a computer.

An individual AI assistant responds when someone supplies a prompt and context. WorkSights AI runs continuously at the organization level, building permission-aware context from operational signals across connected systems. Leaders do not need to know the right question in advance because WorkSights AI can surface relevant changes proactively.

Not currently. Access follows the configured manager hierarchy, so visibility maps to reporting relationships. Benchmarking across role categories has been requested and may be considered for a future release.

WorkSights AI is designed first for small and mid-sized knowledge-work businesses. Its sharpest direct fit is usually an AI-forward organization with at least 10 users and roughly 20 to 150 people, especially a professional services firm such as an agency or consultancy.

Larger deployments are possible. Organizations with more than 100 users can purchase additional plan bundles, while Enterprise is intended for multi-department, multi-entity, or other tailored requirements, often with partner support.

Yes. WorkSights AI connects to cloud systems where work happens, so it can help leaders understand the business whether a team is remote, hybrid, or office-based.

Observer Agents are always-on AI specialists that focus on defined parts of the business. For example, Rev covers sales and revenue, Byte covers engineering delivery, and Vibes covers team health and collaboration. When an Observer notices a meaningful change, it investigates the supporting signals before deciding whether the finding needs a leader's attention.

Skills-Based Reports are scheduled AI briefings built from Skills, which are structured instructions for interpreting work through your priorities, goals, and roles. They give executives a view across the business and managers a focused view of their teams, delivered by email or Slack according to the plan and schedule.

Memory is WorkSights AI's retained understanding of operational history, priorities, patterns, and baselines. It gives Chat with Context relevant background and helps reports become more specific over time. The available history depends on your plan, and its value compounds as WorkSights AI learns how the business operates.

Chat with Context lets a leader ask questions about the business using the context WorkSights AI has already built. It can answer current, company-specific questions without requiring a new upload or a manual briefing because it draws on permitted operational signals and organizational Memory.

The rollout approach is your organization's decision. A practical sequence is to connect the systems, let leadership review the available data, configure roles and reporting relationships, and then decide how access should expand.

Whether and how you communicate the rollout depends on your policies and culture. WorkSights AI provides rollout materials that explain what the platform reads, what it does not read, and how access works.

No. WorkSights AI receives metadata from connected systems. It does not read email bodies, message content, attachments, documents, or files.

WorkSights AI connects through secure, read-only APIs to the cloud systems your business already uses. It processes operational metadata, identifies patterns across tools and teams, and delivers summaries, reports, and Observer insights without requiring employees to submit updates.

Yes. Data is encrypted in transit and at rest, API tokens are encrypted in the database, and authentication uses Google or Microsoft single sign-on. WorkSights AI undergoes penetration testing and has achieved SOC 2 certification. See the Security page for details.

You need a WorkSights AI account registered through Google Workspace or Microsoft 365, plus the required administrative access to the cloud systems you want to connect. There is no software to install. Most teams can complete the initial setup in under an hour.

WorkSights AI is the intelligence platform for your whole business. It connects to the systems where your team is already working and uses AI to understand the work happening across your business. This gives leaders instant visibility into what's really happening: fewer meetings, better decisions, no surprises.

WorkSights AI supports systems including Google Workspace, Microsoft 365, GitHub, HubSpot, Zoom, Notion, and other business tools. See the Integrations page for the current list.

After connecting integrations, configure your team structure, reporting relationships, roles, and work schedules so permissions and context reflect your organization. WorkSights AI then runs continuously. You can also configure Skills-Based Reports and ask questions through Slack or Chat with Context.

WorkSights AI uses secure, read-only APIs and system-level sources such as audit logs. Each connection is authorized by an administrator with the permissions required by that platform.

WorkSights AI uses role-based access. Members see their own data, Managers see their direct reports, Executives can access the wider organization and configure reporting relationships, and Technical Admins can configure connections without seeing team activity. Additional access can be granted or revoked by authorized administrators.

WorkSights AI analyzes metadata from cloud-based audit logs. It does not access keystrokes, screen captures, message content, documents, or files. Role-based access controls determine who can see information inside the platform.

Signals are structured events from connected systems, such as timestamps, interaction types, and changes. WorkSights AI combines these events to understand how work is progressing across the business. It does not need the content of messages, emails, documents, or files to do this.

Modern companies run across many tools, but leadership visibility has not kept up. We created WorkSights AI to give leaders a clear, continuous view of how the business is operating, so they can make better decisions without relying on more status meetings or manual reporting.

Most integrations can be connected in a few minutes when the required administrator is available. WorkSights AI normally begins processing available activity in about 20 minutes.

Yes. WorkSights AI uses read-only connections and does not modify, write, or delete data in connected systems. It receives and processes system-level signals to generate context and insights.

A Technical Admin can configure integrations and system settings without access to operational data unless another assigned role also grants that access.

WorkSights AI uses metadata such as activity timestamps, interaction types, and system events from connected cloud tools. It does not process the content of messages, emails, documents, or files. The focus is the work itself: how it progresses, where coordination happens, and where patterns change.

WorkSights AI closes the gap between what is happening across a business and what its leaders can see. It turns operational signals from existing systems into timely context, so leaders can catch issues earlier, reduce status-chasing, and make better-informed decisions.

Connect your primary communication and collaboration system first, usually Google Workspace or Microsoft 365. WorkSights AI begins processing available signals in about 20 minutes. Add other systems over time to give the platform a richer view across the business.

Yes. Authorized administrators control who can sign in and which role each person receives. Technical Admins can manage integrations without seeing team activity unless another assigned role grants access.

No. The setup is guided, but you may need an administrator who can authorize system-level API or audit-log access.

WorkSights AI connects through secure, encrypted APIs and system-level sources such as audit logs. It receives structured metadata without installing software on employee devices or changing how connected systems operate.

WorkSights AI combines signals across connected systems, compares them with the context and baselines it has built for your business, and identifies meaningful patterns or changes. It then explains what it found and provides the supporting activity so a leader can validate the insight.

You can start with one integration. Many teams begin with Google Workspace or Microsoft 365 and add more systems over time. Each additional source can provide more context about how work moves across the business.

WorkSights AI is for ambitious founders, CEOs, and operational leaders running modern knowledge-work businesses. It is especially well suited to professional services firms, including agencies and consultancies, where work happens across several cloud systems and leaders need a clearer view of the whole business.

Initial setup is required to connect systems and configure people, roles, and reporting relationships. After that, WorkSights AI runs continuously without employees submitting manual status updates. Administrators can adjust integrations, permissions, schedules, and context when the organization changes.

Yes. WorkSights AI connects using the permissions granted through each source system and applies its own role-based access controls to information inside WorkSights AI.

Yes, in most cases. The exact role or permission depends on the platform because WorkSights AI connects to system-level APIs or audit logs.

WorkSights AI uses established platforms including Postgres, hosted by Supabase; Next.js, hosted by Vercel; and DBOS for workflow orchestration. GitHub supports source control and build management.

Microsoft 365 and Google Workspace reports describe activity inside their own systems. WorkSights AI connects signals across multiple systems and interprets how work is progressing across teams, so leaders can understand the business rather than inspect each platform separately.

Yes. Authorized administrators can enable or disable integrations under Services.

Yes. Authorized administrators can update roles, block sign-in, or revoke access at any time.

Yes. WorkSights AI has achieved SOC 2 certification and uses vendors that are also SOC 2 certified. See the Security page for current details.

No. WorkSights AI works with the cloud systems and workflows your team already uses. Employees do not need to adopt another daily tool or change how they record their work.

No. Under our Terms of Service, you retain the rights to your data, and we do not sell it. Our Privacy Policy explains how data may be handled by service providers and how aggregated, anonymized data may be used for benchmarks, reports, and product features.

Use of raw or derived Google Workspace user data follows the Google User Data Policy, including its Limited Use requirements.

No. There is no software to install on employee devices. Create an account, connect supported cloud platforms such as Google Workspace or Microsoft 365, and configure your team structure and access roles.

Yes. Authorized administrators can remove an integration from the settings at any time.

Yes. You need the required administrative access to system APIs or audit logs. The Technical Admin role lets someone configure integrations without giving that person access to operational data unless another role also grants it.

We retain account data for 30 days after cancellation in case the cancellation was accidental. After that, the data is removed from active databases, with backups retained for up to 90 days.

The Activity Dashboard provides a current view of operational activity from connected systems. It helps leaders inspect the signals behind summaries and insights without opening each source system separately. Availability can vary because different integrations provide data at different times.

WorkSights AI uses Amazon Web Services data centers in US East, Northern Virginia, and EU West, Ireland, for European customers.

No. WorkSights AI does not install software on employee devices and does not read message, email, document, or file content. It uses metadata from company cloud systems to help leaders understand patterns in the work. Its purpose is organizational visibility and better leadership decisions, not judging individuals.

The Score estimates how much activity from connected systems is visible against a person's configured workday. It is a directional signal, not a judgment about performance, and it cannot account for work completed in unconnected tools or away from a computer.

Use it as a prompt to investigate context, never as a verdict. You can disable scores account-wide or by user level under Settings > Account > Score Visibility. The core value of WorkSights AI comes from its summaries, reports, and Observer insights.

After authorization succeeds, WorkSights AI confirms the connection and begins receiving the system-level metadata that the integration makes available. It then processes those signals for summaries, reports, Chat with Context, and Observer insights.

Insights update as WorkSights AI processes new signals and builds a clearer baseline for your business. An earlier interpretation may change when more context becomes available. Treat each insight as evidence to review, with the reasoning and supporting activity available for validation.

No. WorkSights AI uses read-only connections and does not modify data or settings in connected systems.

Nothing is installed on a team member's device, so there is no local application to see. WorkSights AI reads permitted audit-log metadata from company cloud services.

Whether and how you communicate its use is your organization's decision. We provide rollout materials that explain the platform, its data boundaries, and its access controls.

BI tools and dashboards show the metrics you have already chosen to track, usually within a defined data model. WorkSights AI continuously interprets operational signals across systems and can surface patterns leaders did not know to query. It adds an awareness layer above existing dashboards rather than replacing them.

WorkSights AI stops receiving new signals from that system and cannot include them in new analysis until the connection is restored. Data from other working integrations continues to be processed.

Some platforms make audit-log or API data available with a delay. WorkSights AI processes signals as each integration provides them, so timing and detail can vary between systems.

Yes. An authorized administrator can reconnect an integration at any time.

Yes. As WorkSights AI processes more activity over time, it builds stronger baselines and a clearer understanding of how your business operates. Connecting more relevant systems can also provide richer context.

WorkSights AI helps leaders make decisions with greater confidence. In practice, that can mean fewer status-update meetings, earlier warning when work drifts, faster preparation for one-to-ones, and less time assembling context from separate systems. Its organizational Memory makes that context more useful over time.

No. Each platform exposes different events, permissions, and history through its APIs or audit logs. Setup requirements and the signals available to WorkSights AI can therefore differ.

Each system records and exposes different types of structured events. The available detail depends on the platform's API, audit logs, permissions, and retention rules.

WorkSights AI processes the signals the system makes available. Insights involving that system may be less detailed until the integration provides more activity or additional relevant systems are connected.

WorkSights AI provides built-in roles, with custom roles available on some plans:

• Member: sees only their own data.
• Manager: sees data for their direct reports.
• Executive: can see all users and configure reporting relationships.
• Technical Admin: can configure integrations without seeing user activity.

The Free plan lets teams of up to 10 people use core WorkSights AI capabilities at no cost. It helps teams experience the product before choosing a paid plan, and it helps WorkSights AI grow through customer use and referrals. Paid plans add capacity, integrations, longer Memory, and additional capabilities.

No. We do not provide refunds or credits when a customer cancels or changes a prepaid subscription. Paid plans can increase user capacity and historical processing, which creates costs during the prepaid period. Review the plan details before upgrading.

Yes. If you upgrade during a plan period, you are charged the difference between the old and new plans for the months, or partial months, remaining in the current period.

No. We do not currently offer a separate nonprofit discount. Nonprofit organizations use the same published plans as other customers.

WorkSights AI is a product of Ascendius, Inc., a Nevada C corporation. The team is distributed across New York, Denver, Lisbon, and Wollongong. The company is bootstrapped and is not currently seeking outside investment.

The most helpful thing you can do is tell other business leaders about WorkSights AI. We are not actively hiring, but you can contact us at careers@worksights.ai.