FuseWorks
  • GETTING STARTED
    • An Overview
    • QuickStart Guide
  • Deep Dives
    • Scopes
    • Webhooks
    • Bundle Create
  • API References
    • Session
    • Bundle
    • Customer
    • Document
    • Tenant
  • Resources
    • OpenApi Spec
  • Swagger
  • Integrate With Us
  • Meet With Us
Powered by GitBook
On this page
  • Usage of Scopes
  • Available Scopes
  • Authorization
Export as PDF
  1. Deep Dives

Scopes

Refers to the specific permissions or access levels that an application can request and be granted to perform certain actions or access certain data.

PreviousQuickStart GuideNextWebhooks

Last updated 5 months ago

Scopes define what resources an application can access via an API. In OAuth 2.0, they manage permissions and enhance security. As part of your onboarding, we will determine the appropriate scope for your business.

Usage of Scopes

  1. Access Control: Limit access to resources, e.g., FUSESIGN:OWN.

  2. Granularity: Offer different access levels.

  3. Authorization: Users consent to requested scopes.

  4. Token Enforcement: Tokens carry scopes to restrict access.

Scopes ensure applications request only necessary permissions, improving security and user trust.

Available Scopes

FuseSign has the following available Scopes

Scope Name
Access

FUSESIGN:OWN

Only permits actions against the business and may modify any resources they have created.

✅ can create bundles, upload documents and perform actions on any bundles where they are the creator of that bundle.

❌ cannot perform other API actions for example modify bundles that are not theirs or perform contact or bundle search operations.

FUSESIGN

Permits actions against the business and may modify any resources within it

Authorization

Users must authorize integrations to be allowed into their account This is how that will appear:

FUSESIGN:OWN scope
FUSESIGN scope