No description
Find a file
Nextcloud bot 3d7fc78b6a
fix(l10n): Update translations from Transifex
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
2026-03-23 00:25:26 +00:00
.github Implement typescript 2026-02-13 10:40:43 -05:00
.tx [tx-robot] Update transifex configuration 2022-10-01 02:18:54 +00:00
appinfo Prepare 3.2.0 2026-03-16 12:51:06 -04:00
css docs(reuse): Add SPDX header 2025-01-20 15:21:33 +01:00
img update screenshots 2025-08-08 10:57:02 +02:00
l10n fix(l10n): Update translations from Transifex 2026-03-23 00:25:26 +00:00
lib chore(i18n): Fix grammar in error message for file sharing 2026-03-18 08:35:40 +01:00
LICENSES ci(reuse): Add reuse check 2025-01-20 15:22:49 +01:00
src hide batch action for respondAction 2026-02-13 11:49:16 -05:00
templates docs(reuse): Add SPDX header 2025-01-20 15:21:33 +01:00
tests Improve testing 2026-03-16 12:13:03 -04:00
vendor-bin/psalm chore: switch from psalm/phar to vimeo/psalm to support php 8.5 2026-01-08 11:35:39 +01:00
.eslintrc.cjs feat(sidebar-tab): adjust to NC 33 breaking changes 2026-01-05 18:18:10 +01:00
.gitignore chore: switch from psalm/phar to vimeo/psalm to support php 8.5 2026-01-08 11:35:39 +01:00
.l10nignore docs(reuse): Add SPDX header 2025-01-20 15:21:33 +01:00
.php-cs-fixer.dist.php docs(reuse): Add SPDX header 2025-01-20 15:21:33 +01:00
AUTHORS.md docs(reuse): Add SPDX header 2025-01-20 15:21:33 +01:00
CHANGELOG.md Prepare 3.2.0 2026-03-16 12:51:06 -04:00
composer.json chore: switch from psalm/phar to vimeo/psalm to support php 8.5 2026-01-08 11:35:39 +01:00
composer.lock chore: switch from psalm/phar to vimeo/psalm to support php 8.5 2026-01-08 11:35:39 +01:00
COPYING first working component injection in files sidebar 2021-03-11 15:03:02 +01:00
env.d.ts Implement typescript 2026-02-13 10:40:43 -05:00
makefile docs(reuse): Add SPDX header 2025-01-20 15:21:33 +01:00
package-lock.json Implement typescript 2026-02-13 10:40:43 -05:00
package.json Forgot vite config rename 2026-02-13 10:45:33 -05:00
psalm.xml refactor(Application): Use modern events in listerners 2025-12-18 11:21:34 +01:00
README.md Remove createdShares and mention warning in readme for groups as approvers 2026-03-13 13:18:29 -04:00
REUSE.toml chore: switch from psalm/phar to vimeo/psalm to support php 8.5 2026-01-08 11:35:39 +01:00
stylelint.config.js vue 3 2025-06-24 11:50:07 -04:00
tsconfig.json Implement typescript 2026-02-13 10:40:43 -05:00
vite.config.js Implement typescript 2026-02-13 10:40:43 -05:00

Files approval

REUSE status

✔ Approve or reject files/folders.

Warning: The DocuSign integration is no longer part of this app and can be installed with this app.

This app is integrated in the files list (Files app).

Admins can define approval workflows: who can request, who can approve/reject. Users can then request approval. Authorized users will be able to approve or reject.

Settings

After installing the app, in Administration settings, there is a section "Approval workflows" where you define workflows.

Workflow definition:

  • A workflow title
  • A list of users, groups and circles who can request approval
  • A list of users, groups and circles who can approve or reject
  • A pending tag: the tag meaning approval was requested and elements can be approved or rejected
  • An approved tag: the assigned tag when elements get approved
  • A rejected tag: the assigned tag when elements get rejected

A pending tag can only be used in one approval workflow. Workflows can be chained. For example, if the approved tag of a workflow A is used as the pending tag of another workflow B, then once a file is approved by the workflow A, it becomes pending for the B one. For an example of a chain involving a leave request that needs to be approved by a manager and then the department head, there is a screenshot below.

Notice: If the approvers are a group the file may be shared with the individual users of the group instead of the group.

Workflow chain

Tag assignment

There are 3 ways to assign a hidden tag to a file/folder:

  • Click the "Request approval" button in Files sidebar
  • Admins can see and use hidden tags like classic tags. So they can be manually assigned.
  • Via the Files Automated Tagging App

Build

Just run:

make dev

or for production:

make build

Release tarballs are hosted at https://github.com/nextcloud-releases/calendar/releases.

Screenshots

1 2 3