add user permissions to folder linux, step by step

What the agent can do

• Filesread_file, write_file, edit_file, grep and glob work in the chat's working folder, and edit_file shows a diff before you accept the change.
• Shellruns terminal commands in local Windows, WSL or an SSH server you own, and judges success by the real exit code. Dangerous commands are blocked.
• Webweb_search finds pages, and http_get reads one documentation page, for example the manual page of a command you want to understand.
• Screenshots and imagesocr reads text from a saved screenshot, and gen_image saves real image files in the working folder.
• Orchestrationtask runs parallel sub-agents, run_on_model sends a hard step to a bigger model, and skills are reusable playbooks.
• Approval modesAuto-run acts at once, Ask first pauses before actions that change something, and Plan only writes a plan and runs nothing.
• Cronruns a prompt on a schedule that you set, and plans survive a restart of the app.
• Modelsconnect a cloud AI provider through a standard endpoint, a model on your own PC, or the built-in model that is ready to use without an endpoint.

Four tasks, start to finish

Create a user for one job

Using a different user account for different tasks keeps the jobs apart, so start with the account. Gridberry runs adduser deployer with Shell, and the system creates a home folder and asks for a password. Then it runs id deployer to show the user ID and the groups. Some people ask for a second user account with the same home folder, but a shared group on one folder is easier to audit. Back up /etc/passwd before the change. In Ask first mode you approve the creation step, and you test the login with a harmless command afterwards. If adduser reports that the name already exists, read the message in the card, pick another name and run the step again. The manual page of your own system, which http_get can fetch, lists the options that differ between systems.

Give a group access to a folder

The search "add permission to user linux" usually ends at one answer: group membership plus the right letters on the folder. Gridberry shows the folder with ls -ld through Shell, proposes chgrp for the group and chmod g+rx or g+rwx for the rights, and never chmod 777. You see each command as a card before you accept it. Afterwards the same ls -ld output shows the new group and letters. Compare the 2 outputs yourself, because the card shows what the system reported, not what was intended. A non-zero exit code on the chgrp or chmod card means the change did not happen as planned. To go back, set the previous group and letters that the first ls -ld output recorded.

Add an administrator through a group

A common question regarding sudo is whether to edit the rules or to use a group. Most systems already let the members of one admin group, named sudo on some systems and wheel on others, run a command as the administrator. Gridberry adds the user with usermod -aG and lists the groups with id. If the rules themselves must change, you run visudo yourself, because visudo checks the syntax before saving and edit_file does not. Keep a second administrator session open while you do it. Plan only helps here: the agent writes the steps as a plan and runs nothing, so a colleague can read it before you switch to Ask first and carry it out.

Fix a permission denied error

If a user can run sudo but still gets permission denied on a folder, look at two causes first. A new group membership applies only after the next login, and the folder's group may lack the needed letters. Gridberry runs id and ls -ld with Shell, and the two outputs show which cause applies. It then proposes one change, such as chmod g+rx, and in Ask first mode waits for your approval. Run the failing action again and read the result. If the error remains, read the exact message in the card, which usually names the path that refuses access, and run ls -ld on that path to see its owner and group.