Admin approval of form submission

I have rigged a couple solutions to this, Just curious if there is something simple I may be overlooking.

Built an app for a school athletics program which is shared to the squad leadership, members, and fans. Upon logging their information, selecting one of these categories (typically via enumlist options)  is a required field. Knowing these bright upstanding scholars as I do however, I can foresee a couple of them possibly aligning themselves- entirely by mistake of course- as 'Admin' position holders, rather than the lesser permissioned 'Athlete' roles.

The question then is this: Can a column's submission remain hidden until approved by Admin? I have filtered these by way of age, and found a couple other shortcuts and always wind up with circumstances the next time which restructure the problem. I can't help but feel like I'm missing a simple button in the column editor. Data validity- maybe an expression I'm missing? Enumlist: Select submissions trigger an action to notify users categorized in higher tiered role "X" that said submission needs to be reviewed before instated...?

Thanks a bunch folks, 

Solved Solved
0 2 256
1 ACCEPTED SOLUTION


@Stomboly wrote:

The question then is this: Can a column's submission remain hidden until approved by Admin?


I'm not sure what you mean by "column's submission remain hidden".   

If I understand the problem, you are providing the ability for users to self-register, including Admin, and the issue is how do you prevent someone from self-registering as Admin and preventing them from doing Admin things until they are approved.

First, it is critical to understand what app account, or accounts, you will be using.   This can help guide you in what and how to implement the app(s) - especially around Admin roles. 

 

Your description implies that you would likely be planning to use the Publisher Pro (public app) account - $50/month for unlimited users.  Be aware that this type of app DOES NOT include login capabilities so you will not be able to match a user with some registration - unless security is not of concern and you plan to use an "on your honor" system of some sort.

Apps that provide authentication of users start at $5/user per month.  Depending on capabilities you wish in the app you may need $10/user per month.  This can get expensive if you are providing an authenticated app for "fans".

You can also go with a Hybrid approach - authenticated app for users who need those privileges and a Public app for those who are unauthenticated users that simply need access to the information and maybe submit publicly accessible data.

What is your plan for the system?

View solution in original post

2 REPLIES 2


@Stomboly wrote:

The question then is this: Can a column's submission remain hidden until approved by Admin?


I'm not sure what you mean by "column's submission remain hidden".   

If I understand the problem, you are providing the ability for users to self-register, including Admin, and the issue is how do you prevent someone from self-registering as Admin and preventing them from doing Admin things until they are approved.

First, it is critical to understand what app account, or accounts, you will be using.   This can help guide you in what and how to implement the app(s) - especially around Admin roles. 

 

Your description implies that you would likely be planning to use the Publisher Pro (public app) account - $50/month for unlimited users.  Be aware that this type of app DOES NOT include login capabilities so you will not be able to match a user with some registration - unless security is not of concern and you plan to use an "on your honor" system of some sort.

Apps that provide authentication of users start at $5/user per month.  Depending on capabilities you wish in the app you may need $10/user per month.  This can get expensive if you are providing an authenticated app for "fans".

You can also go with a Hybrid approach - authenticated app for users who need those privileges and a Public app for those who are unauthenticated users that simply need access to the information and maybe submit publicly accessible data.

What is your plan for the system?

You got it exactly-  that's what I was getting at. I realize after reading it my using the term "hide" was misleading. Glad you got there all the same. Thank you for a thorough explanation and the time required to leave it. My apologies for such a late response.

Thanks again-

S

Top Labels in this Space