starred/cloudbeaver

Fork 0

mirror of https://github.com/dbeaver/cloudbeaver.git synced 2026-03-04 08:52:27 -05:00

Save scripts in the workspace per user #1036

New issue

Open

opened 2026-03-04 11:36:13 -05:00 by deekerman · 13 comments

deekerman commented

2026-03-04 11:36:13 -05:00

Owner

Originally created by @valentintraen on GitHub (Dec 9, 2025).

Hi !

Several of the CloudBeaver users at my company are web developers. They therefore need to regularly purge cookies from their browser and lose their tabs.

It would be great if they could save their sql scripts in the application workspace and not in the browser, and that everyone could only see the scripts they created (a bit like the tabs currently).

Originally created by @valentintraen on GitHub (Dec 9, 2025). Hi ! Several of the CloudBeaver users at my company are web developers. They therefore need to regularly purge cookies from their browser and lose their tabs. It would be great if they could save their sql scripts in the application workspace and not in the browser, and that everyone could only see the scripts they created (a bit like the tabs currently).

deekerman added the

xf:sql editor

label

2026-03-04 11:36:13 -05:00

deekerman commented

2026-03-04 11:36:23 -05:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Dec 9, 2025):

Hi @valentintraen
If I understood you correctly, your developers were simply writing and using scripts without saving them.

The script save button can be found in the left toolbar of the SQL editor, it looks like an old-school 3.5-inch floppy disk. After clicking it, a pop-up will appear where you can change the script name. Scripts created for private connections are visible only to their creators. Saved scripts are available in the side panel on the right (upper toolbar: Tools → Show scripts).

This article about the Resource Manager might also be helpful.

It that's not your case, please provide more information.

@EvgeniaBzzz commented on GitHub (Dec 9, 2025): Hi @valentintraen If I understood you correctly, your developers were simply writing and using scripts without saving them. The script save button can be found in the left toolbar of the SQL editor, it looks like an old-school 3.5-inch floppy disk. After clicking it, a pop-up will appear where you can change the script name. Scripts created for private connections are visible only to their creators. Saved scripts are available in the side panel on the right (upper toolbar: Tools → Show scripts). This article about the [Resource Manager](https://github.com/dbeaver/cloudbeaver/wiki/Resource-Manager#saving-a-script) might also be helpful. It that's not your case, please provide more information. <img width="1340" height="1480" alt="Image" src="https://github.com/user-attachments/assets/4636d4db-411b-4798-a86e-962859ff9c02" />

deekerman commented

2026-03-04 11:36:24 -05:00

Author

Owner

@valentintraen commented on GitHub (Dec 9, 2025):

I had seen this option but it only seems available on administrator accounts, right? I have it but the developer accounts don't have it

@valentintraen commented on GitHub (Dec 9, 2025): I had seen this option but it only seems available on administrator accounts, right? I have it but the developer accounts don't have it

deekerman commented

2026-03-04 11:36:25 -05:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Dec 9, 2025):

Could you describe your configuration? What permissions do your developers have? Common users? Are they using the connections you created in the shared project?

Please check that the Enable resource manager option is enabled in the server configuration. All users have access to creating scripts if this setting is enabled.

@EvgeniaBzzz commented on GitHub (Dec 9, 2025): Could you describe your configuration? What permissions do your developers have? Common users? Are they using the connections you created in the shared project? Please check that the Enable resource manager option is enabled in the server configuration. All users have access to creating scripts if this setting is enabled. <img width="3835" height="1315" alt="Image" src="https://github.com/user-attachments/assets/d0468996-29d3-483f-b664-ce044f7f3071" />

deekerman commented

2026-03-04 11:36:25 -05:00

Author

Owner

@valentintraen commented on GitHub (Dec 9, 2025):

Resource manager is already enabled.
All the devs belong to this ldap group mapping :

My account is mapped the same way but with admin rights

@valentintraen commented on GitHub (Dec 9, 2025): Resource manager is already enabled. All the devs belong to this ldap group mapping : <img width="1069" height="384" alt="Image" src="https://github.com/user-attachments/assets/12b75796-d3dd-45fe-9373-595603a7d262" /> My account is mapped the same way but with admin rights

deekerman commented

2026-03-04 11:36:26 -05:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Dec 9, 2025):

Are they definitely logging into the application under their own user accounts? With the Resource Manager enabled, the only reason I can think of for not being able to save a script is if the user is anonymous (not logged in).

@EvgeniaBzzz commented on GitHub (Dec 9, 2025): Are they definitely logging into the application under their own user accounts? With the Resource Manager enabled, the only reason I can think of for not being able to save a script is if the user is anonymous (not logged in).

deekerman commented

2026-03-04 11:36:27 -05:00

Author

Owner

@valentintraen commented on GitHub (Dec 9, 2025):

Yes, it is certain that they get along well with their user, we cannot do otherwise. And I tested it myself with a test user who is in their group, and indeed, I cannot save a script.

@valentintraen commented on GitHub (Dec 9, 2025): Yes, it is certain that they get along well with their user, we cannot do otherwise. And I tested it myself with a test user who is in their group, and indeed, I cannot save a script.

deekerman commented

2026-03-04 11:36:27 -05:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Dec 9, 2025):

Can you check if that test user can see scripts tab?
Tools → Show scripts

@EvgeniaBzzz commented on GitHub (Dec 9, 2025): Can you check if that test user can see scripts tab? Tools → Show scripts

deekerman commented

2026-03-04 11:36:28 -05:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Dec 9, 2025):

What version are you using now?

@EvgeniaBzzz commented on GitHub (Dec 9, 2025): What version are you using now?

deekerman commented

2026-03-04 11:36:28 -05:00

Author

Owner

@valentintraen commented on GitHub (Dec 9, 2025):

Yes, but in read-only :

(I created this script with my own account)

The last version, 25.3.0

@valentintraen commented on GitHub (Dec 9, 2025): Yes, but in read-only : <img width="2219" height="1239" alt="Image" src="https://github.com/user-attachments/assets/665f21c5-ff1e-481f-aae4-4acd386904b2" /> (I created this script with my own account) The last version, 25.3.0

deekerman commented

2026-03-04 11:36:29 -05:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Dec 9, 2025):

Thank you, we'll need some time to investigate.

@EvgeniaBzzz commented on GitHub (Dec 9, 2025): Thank you, we'll need some time to investigate.

deekerman commented

2026-03-04 11:36:30 -05:00

Author

Owner

@valentintraen commented on GitHub (Dec 9, 2025):

Yes no problem. It looks like scripts are managed like connection configurations: the admin creates them and gives rights to them. Thank you

@valentintraen commented on GitHub (Dec 9, 2025): Yes no problem. It looks like scripts are managed like connection configurations: the admin creates them and gives rights to them. Thank you

deekerman commented

2026-03-04 11:36:30 -05:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Dec 10, 2025):

That's because private connections are disabled in the server configuration.
We are planning to add a permission that allows non-admin users to edit shared scripts.

For now, as a workaround, you can enable private connections. This will add the connection creation button, but it will also allow users to save scripts in the local project.

@EvgeniaBzzz commented on GitHub (Dec 10, 2025): That's because private connections are disabled in the server configuration. We are planning to [add a permission that allows non-admin users to edit shared scripts](https://github.com/dbeaver/cloudbeaver/issues/3699). For now, as a workaround, you can enable private connections. This will add the connection creation button, but it will also allow users to save scripts in the local project.

deekerman commented

2026-03-04 11:36:31 -05:00

Author

Owner

@valentintraen commented on GitHub (Dec 10, 2025):

Okay, for now the workaround will suffice. However, I'm very interested in the future development because allowing users doesn't meet my needs. But thank you, that's already pretty good.

@valentintraen commented on GitHub (Dec 10, 2025): Okay, for now the workaround will suffice. However, I'm very interested in the future development because allowing users doesn't meet my needs. But thank you, that's already pretty good.