Allow for plugs autoconnect

store-requests privileged-interfaces
1

Snap name: lexbox Interface: removable-media, process-control, system-observe, hardware-observe, log-observe Reason:

LexBox is an edge-computing document processing appliance for legal offices. It requires:

  1. removable-media: Access network shares mounted at /mnt/ and /media/.

    • Lawyers scan documents to network shares (e.g., //office-nas/LexBox → /mnt/LexBox)
    • Core functionality - cannot work without this

  2. process-control: Monitor Ollama LLM daemon health

    • Need to detect if Ollama crashes and restart it
    • Essential for appliance reliability

  3. system-observe + hardware-observe: Resource monitoring for observability

    • Track CPU/RAM usage for performance troubleshooting
    • Send telemetry to customer’s APM platform

  4. log-observe: View service logs via lexbox logs CLI

    • Customers need to troubleshoot without SSH access
    • Part of appliance management interface

  5. home: Allow reading documents from user home directories (optional fallback)

Target users are legal professionals with zero Linux knowledge. Manual snap connections break the “appliance” experience.

Store listing: Install LexBox - Privacy-First Document AI on Linux | Snap Store

2

This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.

3

I’ve update the category and subcategory as requested

4

But you picked “classic confinement”, this is not the right one when asking for privileged interfaces :wink:

(Also: the home interface is automatically connecting on desktop installs, no need to request it)

5

This request has been added to the queue for review by the @reviewers team.

6

Hello @cjmsousa, apologies for the long delay on this request!

This is a +1 (#voteFor) from me for auto-connecting the system-observe, hardware-observe, and log-observe interfaces for the lexbox snap, given the snap functionality. Additionally, as mentioned above, the home interface is auto-connected by default so no action is needed.

As for the process-control interface, given that Ollama LLM is a daemon within the snap, restart-condition: always should be sufficient for your described needs. If you have run into issues with this feature that might justify relying on process-control instead, please describe them in more detail.

Lastly, the removable-media interface is rarely granted auto-connection due to the highly-sensitive nature of data on removable drives. In order to be granted auto-connection we require publisher vetting, as this is a private snap, that means you must go through the Publisher verification process as described here: Verified Accounts. Please follow the steps listed and we can proceed with the removable-media request upon verification.

7

Hello @cjmsousa!

This is a+1 (#voteFor) from me as well for auto-connecting the system-observe, hardware-observe, and log-observe interfaces, given the snap’s functionality.

I am on the same page with @elisehdy regarding the process-control interface. If you still encounter problems after trying the suggested workaround, please feel free to ping us :slight_smile:

Finally, while the removable-media interface is indeed security-sensitive, it seems like a reasonable request for this kind of snap. We can proceed with the voting process for that interface as soon as you complete the aforementioned publisher verification. (#askForInfo)