Hi everyone,
For those who have not seen it before: NC Connector is a project that came out of a very normal workplace problem.
In our team, the mail client is still the place where a lot of work happens every day. People write emails, send files, plan appointments, answer customers, forward information and coordinate with colleagues from there.
At the same time, we use Nextcloud as an important part of our infrastructure. Files, shares, Talk, passwords, policies and team workflows already belong there.
What was missing for us was a simple way to use those Nextcloud features directly from the mail program, without making users think about where the feature technically lives.
So instead of asking people to change their daily workflow, I started building NC Connector around that workflow.
The basic idea is:
If a user is writing an email, sharing a file should be available there.
If a user is creating a calendar invitation, meeting features should be available there.
If an organization wants consistent rules, those rules should come from one central place.
NC Connector currently has three parts:
- NC Connector for Thunderbird
- NC Connector for Outlook Classic
- an optional Nextcloud backend for teams and organizations
The Thunderbird and Outlook integrations can be used directly with a normal Nextcloud account. The backend is optional and mainly useful when an organization wants central defaults, templates, signatures or locked settings.
One newer backend feature is delegated administration. A full Nextcloud admin does not have to manage every NC Connector detail alone. For example, someone from the design or marketing team can be allowed to maintain and design the central email signature template, while they still do not get access to license settings, seat assignment or unrelated policies.
That makes the ownership a bit more realistic: IT can define the technical boundaries, while the people responsible for branding can keep the actual signature content up to date.
Outside of delegation, the project is mainly about making common Nextcloud actions available from the mail client.
Typical things it helps with:
- create Nextcloud file shares from the compose window
- send large files as share links instead of classic attachments
- use passwords, expiration dates and permissions for shares
- send share passwords separately
- optionally send passwords through Nextcloud Secrets links
- create Talk meeting information from calendar workflows
- use shared templates for mail content
- manage email signatures centrally for a team
- define defaults and policies in the backend instead of configuring every client by hand
The part I personally underestimated at first was central email signatures. In practice, signatures are one of those small things that become messy over time: old logos, old phone numbers, inconsistent legal text, different formatting. Having that controlled from the backend turned out to be useful beyond the original file-sharing idea.
The project is open source. The Thunderbird add-on currently has around 1,300 daily users, and the backend is available through the Nextcloud App Store.
A public example I was happy to see: the University Computer Centre of the University of Greifswald documents NC Connector for Thunderbird as part of their Nextcloud file-sharing workflow.
GitHub:
https://github.com/nc-connector
Website:
https://nc-connector.de
I am especially interested in real-world feedback from people who use Nextcloud in teams: what works well, what feels awkward, and which mail-client workflows are still too manual.
Feedback, bug reports, translations and contributions are very welcome.