Frequently Asked Questions
Learn how WorkSights gives you visibility into how your business is operating, and how to use it with confidence.
There is no individual opt-out, because WorkSights reads company cloud tools through read-only connections rather than software on a person's device. Your organization decides who is included, which tools are connected and who can see the results, and it can exclude any person or any feature of a tool. WorkSights never reads email bodies, documents or files.
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. Open Settings > Account, select your account, and change Score Visibility on the Overview tab. You can show scores to everyone, to executives and managers, to executives only, or disable them. The score is an optional feature, never the point; many teams run WorkSights with scores off and rely on reports, Insights and chat.
Yes. WorkSights 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 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 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 uses that context when generating summaries and insights. Leaders should still review the supporting activity and speak with the people involved before drawing conclusions.
From each person's work schedule and the activity visible in their connected tools. WorkSights estimates the time each activity represents, adds it up against the scheduled day, and compares it with a target that defaults to 80 percent of scheduled hours to allow for breaks and work that leaves no trace in a tool. The result is an estimate, not a measure of output or quality.
A personal assistant such as Claude or ChatGPT sees one person's world: your inbox, your files, what has already reached you. WorkSights connects once for the whole business and reads the work of every team, with permissions from your org chart. It also runs continuously, so it tells you what you should know instead of waiting to be asked. The two work together: connect WorkSights to Claude through MCP and your assistant knows your business.
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 is built for small and mid-sized knowledge-work businesses, typically 20 to 200 people, and especially professional services firms such as agencies and consultancies. It is not designed for large enterprises; above about a thousand people there is more activity than it can turn into a useful picture. Larger mid-sized organizations can add plan bundles, and the Enterprise plan covers multi-department or multi-entity setups.
Yes. WorkSights connects to cloud systems where work happens, so it can help leaders understand the business whether a team is remote, hybrid, or office-based.
Observers are always-on AI analysts, each covering one part of the business. Rev follows sales and revenue activity, Byte follows engineering, and Vibes follows organization-wide health such as working rhythms and collaboration. When an Observer spots something unusual, it investigates in stages and only brings it to you if the signal holds up, with its reasoning attached. You can read the full chain in Insights.
They are the Daily Executive Report and Daily Manager Report. Every morning at 7 am local time, WorkSights sends each executive a briefing on the whole account and each manager a briefing on their direct reports, by email, Slack and the Insights feed. The reports are built from Skills, the structured instructions that tell the AI how to read the work through your priorities, and from the AI Context you set.
Memory is the structured understanding WorkSights builds of your business over time: priorities, baselines, patterns and how people fit together. It is why chat already knows the context when you ask, why Observers can tell signal from noise, and why reports get sharper the longer it runs. How much history is kept depends on your plan.
It is the chat built into WorkSights: Quick Ask on the Home screen, the chat panel in Insights, and the WorkSights bot in Slack. Ask what the fires were yesterday, or what someone has been working on before your one-on-one, and the answer draws on the activity and memory already collected, so you never upload files or write a briefing first. Conversations are saved so you can pick them up later.
That is your organization's call. A practical order is to connect your tools, let leadership review the picture, set roles and reporting lines, then decide how far access should extend. WorkSights provides rollout materials that explain what it reads, what it does not read, and who can see what.
Not the content. WorkSights receives email subjects and participants, meeting titles and attendees, and file names and actions, but never email bodies, attachments, documents or file contents. Comment text from tools such as Jira, GitHub, Figma or Pipedrive is stored where the tool provides it, and for Slack channels you choose between metadata only and full message content.
It connects read-only to the tools your team already uses, from email and calendar to Slack, code, tickets and your CRM, and reads the work as it happens: who did what, when, and how the work moved. From that it builds a current picture of the business. Observers watch for what you should know, a briefing arrives each morning, and you can ask anything in WorkSights, in Slack or in Claude. Nobody on the team has to change how they work.
Yes. All data is encrypted in transit and at rest, and API tokens are encrypted in the database. You sign in with Google or Microsoft only; there is no separate password. Every connection is read-only, and WorkSights runs server-side: no agent on devices, no keystrokes, no screenshots. WorkSights holds a SOC 2 Type 1 attestation, with Type 2 in progress. See the Security page for the current details.
A Google Workspace or Microsoft 365 account for your organization, plus administrator access to the tools you want to connect. There is no software to install. Setup takes a few clicks and most teams are running in under 10 minutes, because WorkSights imports your people and recent activity from the tools you connect.
WorkSights is the AI platform that knows what's going on across your whole business. It connects to the tools your team already uses and reads the work as it happens, so you can keep up without sitting through status meetings or wading through dozens of emails and hundreds of messages. Because AI can read more than any person ever could, you get the real picture instantly. And nobody has to stop working to tell you about it.
Twenty-six today. Communication and collaboration: Google Workspace, Microsoft 365, Slack, Zoom, Front, Notion. Sales: Salesforce, HubSpot, Attio, Pipedrive. Engineering and design: GitHub, Bitbucket, Atlassian (Jira), Linear, Shortcut, Figma. Projects and delivery: Monday.com, ClickUp, Basecamp, Airtable, Rocketlane, HaloPSA. Time tracking: Harvest, Toggl Track, Everhour. People: Deel. See the Integrations page for the setup guide for each one.
Nothing more is required. Once your tools are connected, WorkSights imports your people and activity and starts running on its own, and the setup flow already asks for roles and reporting lines. Later you can refine work schedules, connect more tools, add AI Context for the account or for individuals, and tune the Observers under Settings > Insights. Daily reports and chat work from day one.
Through read-only connections that an administrator authorizes with each vendor, usually OAuth. WorkSights receives activity records: who did what, when and in which tool. It never writes to or changes anything in your systems.
Through roles and reporting lines. Members see their own data. Managers see the people who report to them, directly or indirectly, never peers or upward. Executives see the whole account. Admins manage integrations and settings without seeing activity. Sign-in access is separate from visibility, so a person can appear in reports without being able to sign in. Owners and Admins can change any of this at any time.
WorkSights reads the activity of work, not its content: no keystrokes, no screen captures, no email bodies, documents or files. Access inside WorkSights follows your reporting lines, so managers see their own teams and nobody sees upward or sideways. It is read-only, hosted in a managed cloud, and SOC 2 Type 1 certified with the Type 2 audit in progress.
Signals are structured events from connected systems, such as timestamps, interaction types, and changes. WorkSights 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.
AI has made teams faster at their own work, but the way leaders keep up has not changed: status meetings, email, Slack and dashboards someone has to remember to check. The more work moves, the further behind the people running the business fall. We built WorkSights so leaders can keep up with what is actually happening across the business without anyone having to relay it.
Most integrations connect in just a few clicks when the required administrator is available. Once an integration is connected, its data starts appearing in WorkSights within about 20 minutes.
Yes. WorkSights 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.
Admin is the role for the IT or operations person who runs the setup. An Admin can connect and manage integrations, add and manage users, change account settings and create custom roles, but sees no one's activity or scores unless they also hold an Executive or Manager role.
The activity of work in the cloud tools you connect: timestamps, who was involved, what type of action happened, titles and subject lines, and system events such as sign-ins. Email bodies, documents and files are never read. Where a tool shares comment or note text, such as Jira or GitHub comments, that text is stored in the activity detail, and for Slack channels you choose between metadata only and full message content.
The gap between what is happening across a business and what the people running it can see. Leaders piece the picture together from meetings, inboxes and chat, and still only hear what others chose to share. WorkSights reads the work itself and brings you what you should know, so decisions rest on what actually happened and problems reach you early enough to coach, not punish.
Connect Google Workspace or Microsoft 365 first; it brings email, calendar, files, chat and meetings in one connection, with recent history included. Setup takes under 10 minutes, activity appears within about 20 minutes, and your first morning report arrives the next day. Add your CRM, project and code tools over time for a fuller picture.
Yes. Owners and Admins decide who can sign in and which role each person has, from the Team page. Sign-in access is separate from inclusion in reporting, so you can keep everyone's work in the picture while giving access only to leaders at first and widening it later.
No. Each connection is a guided flow of a few clicks. You may need an administrator of the tool to approve the access, and a few tools ask for an API key, which each setup guide shows you how to find.
Through secure, encrypted, read-only connections to your cloud tools, authorized by your administrator. There is no software on employee devices and nothing changes in how the connected tools work.
WorkSights 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.
The people running growing knowledge-work businesses of roughly 20 to 200 people: founders, operating partners, COOs and the managers under them. Professional services firms such as agencies and consultancies first, scaling startups second. It also suits the AI consultants and managed service providers who advise those businesses and need to see how a client really works.
Initial setup is required to connect systems and configure people, roles, and reporting relationships. After that, WorkSights runs continuously without employees submitting manual status updates. Administrators can adjust integrations, permissions, schedules, and context when the organization changes.
Yes. WorkSights connects using the permissions granted through each source system and applies its own role-based access controls to information inside WorkSights.
Usually, yes. Most vendors only let an administrator grant the organization-wide, read-only access WorkSights needs. Inside WorkSights, Owners, Executives and Admins can connect services; the Admin role lets your IT team do this without seeing anyone's activity.
WorkSights 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.
Those reports describe activity inside one system, as counts. WorkSights reads the work across every connected tool and tells you what is going on: which client went quiet, what a team dealt with yesterday, where a project stalled. You can ask it questions and it answers from what actually happened, rather than from a usage chart.
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.
No. WorkSights 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.
Yes. WorkSights holds a SOC 2 Type 1 attestation, and the Type 2 audit is in progress. Data is encrypted in transit and at rest, access is read-only, and nothing is installed on anyone's device. See the Security page for the current details.
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. Sign in with Google or Microsoft, connect the tools your team uses, confirm who is in and how the team is structured, and WorkSights imports your people and recent activity. There is nothing to install and nothing for your team to do. Most accounts are set up in under 10 minutes and useful the same day.
Yes. An Owner, Executive or Admin can deactivate a service, or a single connection, from Service Details. WorkSights stops receiving new activity and removes any webhooks it created, and the activity already collected stays. To remove a connection and its history entirely, contact support.
Yes, for setup. The person who creates the account must be a Google Workspace or Microsoft 365 administrator, because WorkSights needs organization-wide, read-only access to the tools. Inside WorkSights, the Admin role can connect and manage integrations without seeing anyone's activity, so your IT team can own setup while leaders own the picture.
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 uses Amazon Web Services data centers in US East, Northern Virginia, and EU West, Ireland, for European customers.
No. Nothing is installed on anyone's device, and there is no screen capture or keystroke logging. WorkSights reads the activity of work in your company's cloud tools: who did what, when, and in which tool. Email bodies, documents and files are never read. For a few tools you can choose to include comment or message text, such as Slack channel messages, and that choice is yours. The person can be the question, but the work is always the answer: it describes what happened and never grades anyone.
An activity estimate: how much of a person's scheduled working day is reflected in the tools you have connected. It is directional, not a judgment of the person, and it cannot see work done in unconnected tools or away from a computer. Treat it as a prompt for a conversation. Scores are optional and can be hidden by role under Settings > Account; the value of WorkSights is in its reports, Insights and chat, not the number.
After authorization succeeds, WorkSights 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 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 uses read-only connections and does not modify data or settings in connected systems.
Nothing is installed on anyone's device and nobody has to change how they work, so there is no local application to see. WorkSights connects read-only to your company's cloud tools and reads the work itself. Whether and how you tell your team is your call; most leaders do, because the team dislikes status meetings even more than they do. We provide rollout materials that explain what WorkSights reads, what it does not, and who can see what.
Dashboards and BI are analytical: they show the metrics you chose to track, looking backwards. WorkSights is operational: it reads what the people in the business are working on right now, including the Slack threads, document edits, ticket moves and CRM updates that never become a number. The dashboard gives you the score; WorkSights tells you how the game is going. It runs alongside your BI, not instead of it.
The service shows Needs attention on the Services page, and WorkSights sends a Connected Service Unavailable notification by email, Slack or in the app, depending on your settings. New activity from that tool pauses until an administrator reconnects it with Refresh Connection on Service Details. Other integrations keep running, and no history is lost.
Most activity appears within about 20 minutes. Some vendors release their records later: Microsoft 365 events can take several hours, and time entries from tools such as Rocketlane are polled every 15 minutes. If activity is still missing after a few hours, check that the person is mapped on the service's Users tab and that the feature is subscribed for them.
Yes. An authorized administrator can reconnect an integration at any time.
Yes. As WorkSights 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.
Hours back every week, and decisions made with more confidence and fewer surprises. In practice: the weekly status meeting becomes optional, you walk into one-on-ones already knowing what happened, and problems reach you early enough to coach rather than react. One customer deleted his team's weekly updates channel because the morning report already told him everything it used to.
No. Each tool exposes different events, needs different permissions and keeps different history, so setup and the detail you see vary. The overview guide for each integration says exactly what WorkSights receives, how it appears and what is not captured.
Because each tool records different events and shares them differently. A CRM reports deal stages and notes, a code host reports commits and reviews, a calendar reports meetings. Each integration's overview guide lists what is captured.
WorkSights 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.
Five built-in roles. Owner holds every permission and can transfer ownership. Executive sees activity across the whole account and can manage settings. Admin manages integrations, users and settings without seeing anyone's activity. Manager sees direct and indirect reports and can edit direct reports. Member sees only their own data. Admins and Executives can also create custom roles that combine these permissions.
There is no catch. The free plan lets a small team use the core of WorkSights at no cost, so you can see what it finds in your own business before choosing a paid plan, and it helps WorkSights grow through customer use and referrals. Paid plans add capacity, integrations, longer Memory, and additional capabilities. See the Pricing page for the current plans.
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 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 [email protected].