Solutions
One application. Defined authority across connections.
Build applications around one integration model for supported operations across configured connections. Application identity and granted scope define the work.
A practical example
A scoped request from your application.
An internal application requests a permitted data inventory for its selected workspace. The enabled metadata interface returns only what that application is authorized to receive.
Illustrative workflow
Review a permitted data inventory.
- Requester
- Your application
- Interface
- Enabled Data API operation
- Scope
- Selected workspace · metadata
Data checks the request.
The enabled metadata operation returns a permitted result to the application. This request does not transfer provider content.
Recorded Rhea activity / actor · operation · outcome
- 01
Identify the application
Associate application requests with their own identity and permitted scope.
- 02
Check each operation
Verify the requested action is allowed for the target resource and supported connector.
- 03
Handle results responsibly
Return the permitted metadata to the application and keep the activity attributable. Content transfer is a separate operation with its own interface and connection-mode requirements.
Architecture and scope
A clear model for your environment.
This is an illustration of the access model, not a runnable quickstart. Available operations depend on each connection; request access to the API reference for your environment. Direct SQL query execution is disabled.