01 / ACCESS
Start in the correct workspace.
An owner manages platform scope. A customer signs in to their own organization. API keys expose only their granted read scopes; a website address does not grant access.
TUCANA SHIELD / CONNECTED SERVICES
From a signal
to a responsible next step.
Understand which functions are available in a private workspace, which require a connected source and which remain a separate action.
02 / OBSERVE
Review dashboards and summaries.
Use the default Grafana dashboard for recorded API outcomes and the service panels for enabled summaries. Check the source, time window and completeness before comparing figures.
03 / INVESTIGATE
Turn a discrepancy into a question.
Review evidence and reports, identify the affected service and assign a responsible person. A missed call, failed voice request or policy denial is not automatically a confirmed attack.
04 / APPROVE
Define the permitted response.
Plan the intended action, target, reason, expiry and rollback with the responsible service owner. The portal records supported approval decisions; external action planning and execution remain separate. The approver must have authority over that system.
05 / ACT
Use an authorized action path.
Call, Chat and VoxVain connectors currently provide no remediation actions. Carry out an approved change in the responsible service, or use a separately enabled and verified action connector.
06 / VERIFY
Check the result and retain evidence.
Confirm the expected outcome from the source system, record the result and revisit the relevant evidence window. An approval record alone does not prove execution.
Choose a task
Understand an API decision
Use the fictional request lab to explore tenant and scope decisions.
Open this workflowReview your organization
Sign in to review authorized customer records and connection status.
Open this workflowUnderstand service activity
Read the exact scope of each prepared communication connector.
Open this workflowRemediation has a separate permission boundary.
Tucana Shield can help organize the evidence and responsibility for a response. These three service integrations do not currently place calls, send messages, generate speech, disable users or change a service configuration. Future actions require their own implementation, scoped credentials, testing and activation.
Start with a defined scope.
Choose your organization, identify the service owner and agree what information should appear. Credentials are installed privately; never send them through the public contact form.