Datroom Database Walkthrough: User Management, Credits, and Best Practices
Explore a detailed walkthrough of the Datroom database, covering user management, application decisions, credit allocations, and best practices for internal notes and session handling.
In this guide, we'll learn how to review and manage user applications in the Datroom database. We will cover how to handle user statuses, update decision labels, manage credits, and add internal notes for declined users. This guide will help you keep your application process organized and clear.
Let's get started
Okay. Doing a Datroom database walkthrough. Start from the top; it's user. Okay, this looks good. We had a few bullet points, such as "Never sold to more than two parties." These bullet points should go under the subheader, followed by a sentence and two sub-bullet points.
Okay, that worked.
That seemed to be fine. I mentioned that we should change this to names we would use for ourselves, which might sound like we are calling ourselves names.
If we don't see it on the sign-in, look at one of our other examples. We have done a number of these, but not this one.
Welcome back sounds a bit friendly. We see applications.
Here we see a Duke on email. We should check this and not allow Duke to receive emails in this system.
When we reach the decision stage, we should change it to either "declined" or "accepted," not just "decision." Green may indicate a positive decision. That's unclear. All right, I'll reject this user.
Application okay, good.
I will approve this user to see if it appears.
This needs to be fixed. The cutting here is not good.
It might be good to have an internal notes section here. If I decline someone, I could add a note explaining why.
We wouldn't send that to them, but it's for our own internal notes on members or users. I'm assigning it to the user as requested. They should change it so it is declined.
If you decline, you should move from under review to declined without giving a reason. Just state declined. This is not exactly correct, like credits remaining.
We have free credits, and then there is a monthly allocation of 1,000. Look at the previous generation of this, because it's 300. They receive 333 credits upon signing up. After that, they can purchase 1,000 credits each month. So it's not available ... This would be 333 credits. A different category would show the total amount spent, such as the total monthly allotment used.
I'm not sure if this token is saved in the browser or why it is pre-populated on this screen or in the search.
The session should follow best practices. I'm not sure if I left this at this stage last time, but I don't think so. I think it's from a different account. Here, this goes to one.
I understand that's the minimum.
If I try two, I can't write two thousand.
I can't write 2,000, get back to 300, or figure out how to do this in this field.
I'm not sure where it says, "1001 available now." Every time I click here, the total available should be different from what you can order for a month.
It should show much more available now.
If you try to go over something, you should be able to pay this over your monthly allotment of 1,000. This should probably be split, right?
Credits remain as requested and are now available. Then, 12 credits are requested, leaving 333 credits remaining. The credits applied should be 12. The order should be clear, because this is unclear. This spacing is incorrect.
If you cancel those 12 credits, they should return to your credit balance. I canceled the order, but the credits were not put back.
This should update correctly.
