# Design company data permissions

Use case · Platforms · Planned API workflow

Canonical page: https://datasdk.ai/use-cases/design-company-data-permissions

Plan access around customer roles and actual workflow needs.

## Who this helps

A product team needs to decide which users can view or act on company activity.

## How to use it

1. List the roles that need company records.
2. Keep lookup credentials on the server and scope access checks.
3. Test read and action permissions before enabling the feature.

## Illustrative example

A proposed platform might let analysts review records while restricting account updates.

## What to check

The platform must implement its own access model; API access is coming soon.

## How Data SDK fits

The full Data SDK API is coming soon. Platform and AI-agent workflows are planning examples. Confirm access, data delivery, usage, branding, and resale terms before building or selling a feature.

These are suggested workflows, not a list of built-in integrations. Use your own approved analytics, CRM, and research process where needed. Matches and fields vary. A company match does not identify a person or prove buying intent.

## Related reading

- [API key](https://datasdk.ai/glossary/api-key): An API key is a credential or identifier used when software accesses a service.
- [Tenant isolation](https://datasdk.ai/glossary/tenant-isolation): Tenant isolation keeps one customer's data and actions separate from another's.
- [Least privilege](https://datasdk.ai/glossary/least-privilege): Least privilege gives software only the access needed for its task.
- [Offer identification in a website-builder product](https://datasdk.ai/use-cases/offer-identification-in-a-website-builder-product): Plan identification as a clearly explained optional website capability.
- [Build a tenant-safe company lookup service](https://datasdk.ai/use-cases/build-a-tenant-safe-company-lookup-service): Plan company lookup around authorized customer contexts.
- [Design a graceful no-match experience](https://datasdk.ai/use-cases/design-a-graceful-no-match-experience): Avoid misleading users with guessed names or stale company cards.

[Glossary](https://datasdk.ai/glossary) · [Use cases](https://datasdk.ai/use-cases) · [Comparisons](https://datasdk.ai/vs) · [For businesses](https://datasdk.ai/for-businesses) · [For builders](https://datasdk.ai/for-builders)