My SLAs

A single dashboard answering "where do I need to focus across all my matters?" — every upcoming key date the user has read on, traffic-light tiered, sorted critical-first, with a built-in way to delegate.

What it is

Alt.MySlas is a portal home / fee-earner dashboard widget. Drop it on a page that isn't bound to a single matter (like a partner's home page) and it surfaces every key date the user can see across their entire portfolio of matters, organised so the most urgent items are on top.

It's the cross-matter companion to Alt.SlaWatch, which answers the same question for a single matter. Same pill semantics, same action panel — different scope.

Why it exists

Before: A partner reviewing weekly SLA standing across their team had to open each matter individually, find the Key Dates V2 widget, eyeball the dates, then context-switch to the next matter. Five clicks per matter, no triage view, no way to see "which matters have ANYTHING overdue right now?"

Now: One dashboard. Three buckets. The 3 actionable items are above the fold; 41 noisy enquiry rows can be filtered out with one chip click; 6 stale-but-known items are collapsed by default so they don't hide what needs attention this week.

How it helps a partner triage in 30 seconds

1. "Needs action now" is open and red. These are the things that will hurt the firm if nobody touches them this week.
2. "Coming up" is amber/green. The pipeline. Shouldn't need partner attention but you can see it.
3. "Stale Backlog" is collapsed. Items overdue beyond the staleness threshold (default 30 days). Acknowledged backlog — open the section if you want to clean it up.

Each pill is a card that self-explains: the date, how overdue/imminent it is, an actionable why-it-matters sentence, and meta strip showing the matter's phase, the primary owner, and last activity. Click the card to expand the action panel inline:

• Comments — see and add chronology comments without leaving the dashboard.
• Reminders — view, add, and remove reminders on the key date.
• Phase transitions — Mark Done / Mark Missed / Mark Removed close the pill from the queue.
• Create task — opens the standard Sharedo new-task blade with the matter pre-set as parent and the title + description pre-filled from the pill data ("Action: Instruction Date on D.MD.26.00103" with the why-it-matters context in the body). Templates configurable per placement.
• Open matter — opens the parent matter in a new tab when the partner needs the full picture.

Configurable per placement

Out of the box the widget surfaces the most useful behaviour with sensible defaults. When a configurator wants to tune it, the designer exposes:

• Tier thresholds — redDays, amberDays, staleDays.
• Scope — what counts as "my" matters; which key-date types to include; max items per page.
• Display — grouped by matter (default) vs flat list; tooltip context toggles.
• Owner-role priority — which participant role names to walk when finding "the responsible fee-earner". Default covers primary-owner, matter-owner, responsible-fee-earner, owner so the badge resolves on every Sharedo build we've seen (canonical Sharedo, multiple client builds, and the Alterspective alt- branch).
• Partner-role priority — same idea for the partner-on-record.
• Task templates — custom title and description templates with token interpolation ({dateName}, {matterRef}, {ownerName}, {whyText}, {dueDate}, …) for the Create task affordance. Defaults pack the salient context so the assignee sees what the task is about without opening the matter.

What it costs

Same compliance footprint as Alt.SlaWatch. Reads via Sharedo APIs (/api/search/sharedos, /api/keyDates/for/..., /api/comments/..., /api/sharedo/{id}/phase) — these are platform internal APIs, re-checked on each Sharedo upgrade. No external SaaS calls. No data leaves the tenant.

The widget is security-trimmed by the platform: it only shows matters the user has read access to under their own roles or their team's roles. Two partners viewing the same widget see different matters.

Where it fits

Built and shipped by Alterspective (Alt.MySlas namespace). Source lives in src/widgets/my-slas/ in the Alterspective Widgets repo. Deployable to any Sharedo tenant via the standard widget deploy path.

Pairs naturally with:

• Alt.SlaWatch — the same pill UX scoped to a single matter. Same action panel; users learn it once.
• Alt.MyProfileCard — surfaces the user's identity, contact hours, and workload tile counts. Appears alongside MySlas on the portfolio home page.

Engagement model

• Tier: T2 (production widget, multi-version, configurable, live on tenants).
• Foundry version: consumes the local runtime helpers (bridge); the src/ pipeline now builds against the published @alterspective-engine/foundry package (the remaining root-level widget sub-packages are migrating alongside it).
• Primary repo: alterspective-widgets — src/widgets/my-slas/.

For engineering-side technical detail, AGENTS.md → Alt.MySlas. For partner-side workflow, this brochure.

How it's built

Git is the single source of truth — the component lives at src/widgets/my-slas. Deployment is to the Sharedo IDE; the manifest defines how the platform loads it.

How to use it

Add My SLAs to a portal page via the Sharedo Portal Designer (it appears under Alterspective / Dashboard). Configure it via the designer cog on the placed widget.

For the authoritative configuration fields and behaviour, see the component's designer help panel and the source linked in the footer.