FAQ
FAQ
In many companies, database systems are managed not by executives themselves, but by designated SYSAdmins. Since these admins have access to critical company data, a poorly handled transition when they resign can lead to serious problems—ranging from lost access to important systems to legal disputes over data ownership.
Ragic acts solely as the "service provider" for your database and does not intervene in internal disputes. We cannot revoke or transfer SYSAdmin permissions without the consent of the current SYSAdmin. Even if a company requests Ragic to suspend a former employee’s account or reassign admin rights, we must adhere to our terms of service to protect data security.
We recognize the rightful owner of a Ragic database as "the person who originally registered the database" and established the contract with Ragic, based on their email address. Unless there is a clear, authorized request from that account, we are not in a position to make changes to access permissions.
Here is an explanation of how Ragic defines database ownership, along with suggestions for avoiding disputes.
(If you’d rather skip the explanation and want to know what to do, click here.)
In Ragic, there are two types of accounts:
1. Database Account: the shared workspace for your company or team.
2. User Account: tied to an individual email address. A database can include multiple user accounts.
To start using Ragic, someone must register a "Database Account" by entering a database name (Database Account), username, and email (User Account). This person becomes the first user, the default SYSAdmin, and the account owner, since the contract with Ragic is tied to their email.
As the SYSAdmin, they can invite teammates, assign admin rights, and manage the database setup and design. SYSAdmins can also back up and restore the database structure.
If you’re not a SYSAdmin, you won’t be able to access backups or change database settings—even if you’re the company owner, billing contact, or a Ragic support rep. This ensures your data remains secure and that only authorized users can make changes.
Disputes often arise when companies mix personal and business accounts. For example, an employee might use their personal email to register a Ragic account for testing. Later, that same account ends up being used as the company’s production database, with no proper transition to a corporate-managed setup. At this point, the employee may unintentionally become the "owner" of the company’s entire database system. If the employee leaves without handing over access, the company could be locked out of its own system.
To avoid such issues, we strongly recommend the following:
When your company decides to use Ragic, do not continue using the test database created with a personal email. Instead, register a new database account using a shared company email. You can then migrate the design and structure using Ragic’s backup and restore feature.
Note: When backing up and restoring, we recommend selecting Backup database definition only. This option transfers the database design without including test data.
If you also need to transfer data, you can back up the entire database, but be cautious with the "user list" to avoid overwriting user permissions. Before restoring, add the shared company email as a user and assign it SYSAdmin rights in the test database. Otherwise, restoring the user list may overwrite existing users and temporarily prevent access for the company email account.
After restoring, remember to set any private email accounts to SUSPENDED, if needed.
When a SYSAdmin leaves the company, it is essential to transfer Ragic SYSAdmin rights to someone else. You can do this in one of two ways:
(1) Transfer SYSAdmin Role: Assign at least one company email as a SYSAdmin, and set your own account to SUSPENDED.
(2) Transfer the Email Account: Hand over the email account that holds SYSAdmin rights to someone else in the company.
