You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a discussion tonight at Code for Tampa Bay meetup wanted to document a thought.
I don't have a specific use case in mind, but I know it's been discussed in the past as well. We should document the current way updates are approved. I'm not 100% sure the system now. My recollection is shelter updates were in real time between a super admin and other volunteers where a quick level of trust was built. Insert something about scale here.
The text was updated successfully, but these errors were encountered:
Draft changes can be created by users, but an admin must approve it. Admin users create a draft, but auto-approve it immediately. Drafts are a record of history for each record. In theory we could setup a view that allows a user to restore a previous draft version.
After a discussion tonight at Code for Tampa Bay meetup wanted to document a thought.
I don't have a specific use case in mind, but I know it's been discussed in the past as well. We should document the current way updates are approved. I'm not 100% sure the system now. My recollection is shelter updates were in real time between a super admin and other volunteers where a quick level of trust was built. Insert something about scale here.
The text was updated successfully, but these errors were encountered: