Requirements Gathering and Scoping Questions

Acceptance Criteria

1. Functional — creation & access

• Given an authenticated admin user, when they create a shareable link for Dashboard D, then system returns a unique token and URL that grants view-only access to D for allowed viewers.
• View-only: shared view must not expose edit/save/share buttons; all write APIs return 403.
• SSO: users accessing URL are routed through SSO (SAML/OAuth) prompt if not already authenticated. If SSO succeeds and user belongs to the same tenant or is explicitly allowed, they see the dashboard.

2. Configurable expiry & admin override

• Creator may set expiry TTL (min 1 hour, max org-configurable). After expiry, token returns 410.
• An admin (tenant admin) can revoke/extend any token; revocation takes effect immediately.

3. Multi-tenant isolation & ACLs

• Token is scoped to tenant; cross-tenant access returns 403. Tokens cannot access dashboards outside original tenant.
• If dashboard permissions change (dashboard deleted or moved), token becomes invalid (410 or 404 depending).

4. Edge cases

• Expired token => 410 Gone
• Revoked token => 403 Forbidden
• Deleted dashboard => 404 Not Found
• Concurrent revocation/validation: latest state enforced

5. Non-functional

• Rate limit: 200 token validations/sec per tenant; excess => 429
• Latency: token validation + dashboard render metadata response < 300ms P95
• Audit: every token create/validate/revoke logged with actor, IP, timestamp

API surface (examples)

Create:

POST /api/v1/tenants/{tid}/dashboards/{did}/share
Content-Type: application/json
Body: { "ttl_hours": 72, "allow_list": ["example@partner.com"] }
Response 201 { "share_url": "https://app/x?token=abc", "token": "abc", "expires_at": "..." }

Validate (used by CDN/gateway):

GET /api/v1/share/validate?token=abc
Response 200 { "tenant_id": "t1", "dashboard_id": "d1", "permissions": ["view"], "expires_at": "..." }
Response 410 / 403 / 404 as appropriate

Revoke:

POST /api/v1/share/revoke
Body: { "token": "abc" }  -> 200

Definition of Done

• Unit + integration tests covering create/validate/revoke, SSO flow, expired/revoked/deleted cases.
• E2E test demonstrating SSO-authenticated viewer sees view-only UI.
• API documented (OpenAPI), example client snippets provided.
• Load test shows validation P95 < 300ms at 200 req/s and correct 429 handling.
• Security review completed: token entropy >= 128 bits, HTTPS only, CSRF/XSS mitigations.
• Audit logs available and searchable; monitoring/alerts for error rate/rate-limit breaches.
• Feature flags to rollout per-tenant and migration plan for existing dashboards.