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.

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.

The two tools serve different purposes:

• Claude for Excel is a general-purpose LLM assistant for Excel. It helps with formulas, templates, and spreadsheet logic, but is not natively tied to Daloopa's structured data.
• Scout is purpose-built for buy-side analyst workflows. It produces outputs structured the way an analyst would build them, natively incorporates Daloopa data, and hyperlinks every datapoint so you can audit and refresh figures directly.

Scout currently runs on Claude (Anthropic). We evaluate underlying models on an ongoing basis and may add or change providers over time.

Scout meters usage by dollar cost rather than raw tokens, with soft and hard caps. This keeps billing predictable as Scout routes requests across multiple underlying models.

Not today. Scout does not persist preferences between sessions by default. Skills integration is on the roadmap.

No — restated numbers are returned only when you explicitly request them.

This is on our roadmap. Reach out to your account team if this is a priority for your team — customer demand directly informs sequencing.

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. 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.

Sessions last approximately one week of inactivity, and remain active indefinitely with regular use. SSO sessions may expire sooner depending on your identity provider's token refresh policy.

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.