ppetrov

ppetrov

Hello guys,

I am looking for an advise here. I am trying to build a system which will be tenant application with organizations and users. Under each organization there will be a dossier for a visitor/patient. Under it there will be other different types of records. The organization will have an owner which will be granting access to the different users via records in the database. For example Owner1 adds User2 grating full access as internal over all records under that organization. Or Owner1 adds User2 as external user which will have access only to a single dossier.

The access should be checked each time a dossier is opened under that organization with the assigned access level. If such does not exist the current user will be routed away with error.

Eventually not all users will be granted access over all records but only to few. Also some users would only have read-only permissions without the option to create/edit/delete records.

That is a simple example of what the app is suppose to do. The problem i am having is - should i use Scopes for the granular access or i should just build my own approach which eventually would overlap the Scope functionality to certain level. Or maybe a mix of both - Scopes and custom rules?

To me if i have the organization_rules table which will have the allowed user along with the either resource(s) or full access then the scope for organization might be redundant considering upon creation that field will be populated when being saved. Then when pulling the record and checking the access if the user can read/write etc. then maybe it does not need scopes. Or maybe i don’t understand the scopes very well and my goal can be achieved with it.

Any help is welcome here.

Showing Posts 1 to 2

ppetrov

ppetrov OP

Solved by this topic.

garrison

garrison

Keep in mind that Scopes, like Contexts, are just a pattern rather than something innate to Phoenix as a framework. That’s why most of the documentation is about integrating with the generators rather than scopes themselves.

The point being: if you want to adjust that pattern to fit your needs, you can do so in any way you please. There are no rules.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews