Frequently Asked Questions

The add-in is distributed exclusively through the official Microsoft add-in stores. There is no standalone executable — the add-in is JavaScript-based and runs entirely within the Office 365 ecosystem as a web app, following the latest Microsoft add-in requirements.

You can install it through:

• The Microsoft 365 admin center (recommended for organization-wide deployment)
• The user-facing add-in store inside Excel (for individual users)

For step-by-step instructions, see Getting Started.

No. The add-in is only available through the official Microsoft add-in stores. We do not provide a standalone executable or silent installer. For organization-wide rollout, your Microsoft 365 administrator can deploy the add-in through the admin center.

Updates are delivered automatically for installations through the official Microsoft add-in stores. If your add-in was sideloaded, you may be stuck on a legacy version — please contact your IT department and share the official installation instructions to ensure you receive future updates.

Installation through the Microsoft add-in store is managed by your organization's Microsoft 365 administrator. If you cannot install the add-in yourself, please reach out to your IT department and share the administrator installation guide.

That's expected. The add-in no longer installs onto your computer directly, but you can open it from inside Excel, on the ribbon.

Most stuck-update states are resolved by reloading the add-in directly from the task pane. To do this, click the chevron (⌄) in the top-right corner of the Daloopa task pane and select Reload from the menu. This fully reloads the add-in without closing Excel.
If the issue persists after reloading, restart Excel and reopen the add-in. If you still see the issue, contact support with a screenshot and the company or model you were working on.

Yes — SBOMs are available on request for security and compliance reviews. Contact your account team.

Administrators can manage user access including provisioning and offboarding through the admin console. Contact your account team for details on access controls available to your plan.

Scout is an Excel-native AI assistant for financial modeling. Describe the model or analysis you want and Scout builds it in your workbook using Daloopa data, with a link on every value back to the source filing or disclosure.

Building a model, whether from a blank sheet, into your own template, or ported to a new ticker. Also updating one with a newly reported quarter.

It depends on your plan. Launch Scout with the Switch to Scout button in the upper-right of the add-in's home screen. If Scout is in your plan you can start prompting immediately. If it isn't, the prompt box is disabled. Contact [email protected] to explore access options.

Claude (Anthropic). We evaluate underlying models on an ongoing basis and may add or change providers.

Claude for Excel is a general-purpose LLM assistant for Excel. It's good with formulas, templates and spreadsheet logic, but not natively tied to Daloopa's structured data. Scout is built for buy-side analyst workflows: output structured the way an analyst builds it, Daloopa data natively, and every value linked to its source so you can audit and refresh it.

Usage is metered in credits. Monthly allowance set by your plan, and some firms share a pooled allowance. It resets at the start of each calendar month. At the cap, new requests are blocked until the reset or until your account team raises it. Failed requests don't cost credits.

Yes, through Global instructions. Open the three-dot menu, select Settings, and add the directions Scout should follow across sessions: formatting, units, colours, layout, naming conventions.

Yes. Open the three-dot menu and select Chat history to browse, resume, rename, delete or search past conversations. They're stored in your browser profile, so they don't carry over to another machine and are removed if you clear browser data.

Scout applies Daloopa's built-in modeling conventions automatically, and offers prompt chips as starting points. Uploading your own conventions as a reusable skill isn't available yet. Use Global instructions for standing directions, and the Prompt Library for examples. If shared or user-authored skills matter to you, tell your account team.

No. Scout uses as-reported figures unless you ask for restated ones, which it can retrieve. Separately, when a company changes the shape of its reporting, such as moving a segment or renaming a line, ask Scout to recast the affected periods and it will. It won't do that unprompted.

No. Scout uses Daloopa data only. It does not use external connectors or web access.

A chat answer comes back in under 10 seconds. A step that writes to the sheet is around 2 minutes but varies a lot. A full three-statement model ran 70 minutes to a bit over 2 hours in our tests. You can run more than one session at once.

Excel needs to stay open, and you approve the plan before anything is written. Once a run starts you can leave it going and do other things, but there's no scheduling.

No, Excel only.

See Scout security and data handling, alongside Security and Architecture.

Hub is the current name for the platform you access at marketplace.daloopa.com. The product was renamed from Marketplace to Hub to reflect its expanded scope, which now includes data monitoring, company pages, Skills and reports, and an AI agent — in addition to model downloads. The URL still uses the legacy domain for the time being.

Yes. Daloopa Data subscribers can download datasheets and models directly from the Hub. The Excel Add-in is not included in this tier.

Some plans cap the number of companies a user can subscribe to. When a limit is set or lowered (for example, after a plan change), it applies from that date forward to your total subscribed companies.

A self-service portal covering API key rotation, usage tracking, and subscription management is on our roadmap for 2026. Until then, contact your account team for these requests.

Yes. You keep full access to the data offline. The source links and the add-in need a connection, since the links open a web page and the add-in pulls from Daloopa's database, so both resume working once you're back online.

Yes. Daloopa supports SSO via OpenID Connect (OIDC) through Microsoft Entra. Authentication is required to use the add-in and to access protected content on the Hub (such as source pages), though the Hub itself is publicly accessible without login.

For setup details, see our SSO documentation.

Daloopa's SSO is OIDC-based (via Microsoft Entra) and SAML 2.0 is not currently supported. Our OIDC implementation delivers equivalent outcomes: you retain full control over who can access Daloopa through your Entra environment, including user provisioning and deprovisioning.

If SAML is a requirement for your organization, please reach out to your account team to discuss your needs.

Yes. SSO-only login is supported as a per-customer setting. When enabled, password authentication is disabled for all users on the account and login is restricted to your configured SSO provider. An admin must enable this; contact your account team to turn it on.

Yes. Once SSO is configured for your organization, users authenticate into the add-in through your identity provider rather than entering an email and password.

Note that authentication and installation are separate concerns: anyone can install the add-in, but using it requires authentication — via SSO or email and password, depending on your account's configuration.

Daloopa uses different authentication mechanisms depending on how you're accessing the platform. Session lifetimes are scoped to each mechanism independently.

• Regular app usage (Hub and Excel add-in). Authentication uses short-lived JWT sessions that renew automatically while you're active. SSO sessions may expire sooner depending on your identity provider's token refresh policy.
• API access. API requests are authenticated using API keys. Session lifetime is tied to the lifetime of the API key itself — keys remain valid until they are revoked or rotated by an administrator.
• MCP access. MCP connections use a separate OAuth token managed internally by Daloopa. The token is exchanged directly with the connector through a secure channel and is not exposed to end users. Tokens refresh automatically.

Most SSO issues are resolved by clearing your browser cache and retrying. If the issue persists, contact support with your browser, OS, and identity provider details.

Daloopa operates a multi-tenant, shared cloud infrastructure hosted on AWS. Customer data is logically isolated. All data is encrypted in transit (TLS 1.2) and at rest (AES-256), and user data stored by Daloopa is strictly limited to account identifiers (email addresses) and usage telemetry. Daloopa does not offer dedicated tenant environments.