nextcloud / nextcloud/tables

Permission to only create row through a view not grantable

Open
#2,901 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Steps to reproduce
  1. Create a table with 3 columns, one of them is set to be non obligatory
  2. Create a view that only includes the two obligatory row but not the optional one
  3. Set permission on the view to a group and only allow them to create entries (not to see / edit existing ones)
Expected behavior

Users with permission on the view should be able to create new rows in the table by filling data into the two obligatory fields of the table.

Actual behavior

Tables when opening the view shows a "Ressource not found" because the group has no access to the table itself. Adding the permission to see the existing data inside of the view lets the user also insert data to the table through the view

Tables app version

2.2.2

Browser

No response

Client operating system

No response

Operating system

No response

Web server

No response

PHP engine version

No response

Database

No response

Additional info

No response

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

Start by reproducing the permission flow described for a table, a view, and a group allowed only to create entries. Trace how opening the view checks access to the underlying table and compare that with the create permission. Done means an authorized user can create a row through the view without being able to see or edit existing rows.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authorization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.