Add AI administrative transparency and capability status
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- php
- Domain
- accessibility, backend, frontend
Research direction
Start by inspecting LibreSign’s current administration and Policy Workbench layout, then compare it with Nextcloud AI administration patterns and official Vue components. Prototype capability status, policy entry points, and the data-processing notice, including empty, unavailable, and error states, before implementation. Define done by meeting the listed privacy, accessibility, documentation, and test requirements; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Description
Goal
Give LibreSign administrators a clear, Nextcloud-native view of AI availability and LibreSign policy state without duplicating provider configuration or inventing trust metadata.
This issue is part of the AI foundation epic.
Administrative experience
The settings UI should explain:
- LibreSign uses AI capabilities configured by the Nextcloud administrator;
- technical availability comes from Nextcloud Task Processing;
- LibreSign policy decides whether each supported LibreSign capability may be used;
- depending on the configured provider, document content may be processed outside the Nextcloud instance;
- provider/model configuration remains in Nextcloud.
Show only capabilities that the current LibreSign version actually knows how to consume.
Do not create dead toggles for roadmap features.
Provider metadata
Display only provider/trust/privacy metadata exposed through supported public Nextcloud contracts.
Do not:
- infer local/remote processing from provider app names;
- maintain a provider trust table;
- implement an Ethical AI Rating locally;
- equate local processing with ethical/trusted processing.
If no authoritative metadata is available, use neutral explanatory language.
UX and prototype requirement
Before final implementation:
- inspect current LibreSign administration/Policy Workbench layout;
- inspect Nextcloud AI administration patterns and official Vue components;
- produce a concrete UI proposal or prototype for capability status, policy entry points and the data-processing notice;
- define empty/unavailable/error states;
- verify that the screen does not imply LibreSign configures the provider.
The interaction should be understandable to an administrator who knows LibreSign but not Task Processing internals.
Contextual documentation
Provide contextual access to the LibreSign documentation where it materially helps administrators understand:
- Nextcloud-side prerequisites;
- LibreSign AI policies;
- data-processing implications;
- unavailable capability troubleshooting.
Use the project's established help affordance where possible rather than adding ad-hoc external links.
Accessibility
Use standard Nextcloud components and preserve:
- keyboard navigation;
- accessible labels/descriptions;
- responsive layout;
- understandable status text independent of color.
Tests
Cover at least:
- no supported AI capability available;
- one supported capability available;
- multiple capabilities with different policy state;
- provider/capability disappears;
- missing optional provider metadata;
- frontend does not display a capability that LibreSign cannot consume;
- policy denial is represented without implying the provider is unavailable.
Use Playwright for important administrator flows when consistent with current settings coverage.
Done when
- Administrators can distinguish technical availability from LibreSign authorization.
- No provider/model credentials or selection are duplicated in LibreSign.
- The data-processing notice is accurate without unsupported trust claims.
- The UX has been prototyped/reviewed before implementation.
- Accessibility and empty/error states are covered.
- Contextual documentation access is available where appropriate.
- Automated tests cover representative capability/policy states.
- Dominant language
- PHP
- Stars
- 844
- Forks
- 176
- Avg merge
- 14h 3m
- Merged PRs (30d)
- 344
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LibreSign/libresign
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPossibly taken @vitormattos claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#9366 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
LibreSign/libresign#9007 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#8284 · 5 comments ·
Maintainers usually reply within 1 day
-
frontend javascript technical debt
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
All issues in LibreSign/libresign
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Automattic/blocks-engine#6318 ·
Maintainers usually reply within 1 day
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
35-feedback
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day