nextcloud / nextcloud/approval
Finer-grained access control for Request Signature
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 20m
- Merged PRs (30d)
- 4
Description
When I setup an approval workflow, I need to define the group of users (or the users themselves) that can request the approval. Thus, only those users will be able to trigger the workflow.
It makes sense to put in place the same restriction for the Request Signature action, as of now if the Docusign integration is enabled all the users have access to it.
This functionality would come naturally if signing the document would be considered one of the possible ways to approve a document.
Contributor 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.
Research direction
Start by tracing the approval workflow's user or group restrictions and the Request Signature action when the Docusign integration is enabled. Determine how access is currently granted, then define and verify behavior for restricting signature requests to specified users or groups, including how this relates to document approval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100