nextcloud / nextcloud/mail

Centralized, Admin-Managed Email Signatures

Open
#12,224 4 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Is your feature request related to a problem? Please describe.

Currently, email signatures in Nextcloud Mail are fully managed by individual users.
Administrators have no way to centrally define or enforce signatures.

This leads to:

  • Inconsistent external communication
  • Violations of corporate identity (CI) guidelines
  • Increased support and configuration effort

This is especially problematic in organizations with compliance or branding requirements.

Describe the solution you'd like

Introduce a centralized email signature management feature at the admin level that allows:

  • Managing signatures:

    • per user
    • per user group
    • per mailbox
    • global default
  • Editing signatures in the admin settings

  • Controlling user permissions:

    • Make signatures read-only (locked)
    • Allow or disallow user overrides
  • Clear precedence rules (e.g. mailbox > user > global)

Describe alternatives you've considered
  • Consistent and professional email communication
  • Reduced user misconfiguration
  • Lower administrative overhead
  • Better support for organizational use cases
Additional context
  • Signature preview in admin settings
  • Multiple signatures per user or mailbox
  • Signature selection based on sender address

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start by locating the existing user-managed signature settings and the admin-settings entry point, then clarify precedence, locking, overrides, and multiple-signature behavior before defining the implementation scope and acceptance tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.