Getting Started With Ehubauscom
Most people approach this platform expecting it to work like any other dashboard, and they hit a wall within the first hour. The UI is clean enough, but the backend routing logic is not intuitive unless you understand how the permission chains actually resolve. I spent three weeks troubleshooting a deploy script that kept failing because the default admin role does not inherit the batch_export permission, even though the docs suggest it should. The workaround was adding a custom role mapping in the config file at /etc/ehubauscom/roles.yaml, then restarting the worker process. The onboarding flow requires you to set up an organization unit before you can create any users, which makes sense from a data isolation perspective but adds an unnecessary step if you are just evaluating the tool for a small team. The API token generation endpoint is at /api/v2/auth/tokens, and you need to pass both a scope parameter and a TTL. If you skip the scope, the system defaults to read-only access, which trips up a lot of beginners who assume they will get full admin rights immediately. Feature-wise, the bulk import tool supports CSV and JSON, with a 50MB file limit per upload. Processing a 40MB file with around 120,000 records typically takes about 45 seconds on a standard SSD setup, give or take 10 seconds depending on your row complexity. The parser is forgiving with missing columns but will silently drop rows that have mismatched data types, so always run the dry-run mode first. It outputs a summary table showing how many records passed validation versus how many failed, broken down by error type.
Security is where this tool actually shows its teeth. Role-based access control is granular, with permissions scoped to individual resource types. You can restrict a user to only viewing assets in a specific region, or limit API access to certain endpoints during business hours. The audit log captures every mutation, including the previous and new values, which is useful for compliance reviews but generates roughly 2GB of data per month for an active team of 50 people. You need to configure log retention in the storage settings, or the disk fills up fast. Two things people get wrong about this platform. First, the session timeout is not a global setting, it is configured per application unit. If you have multiple services sharing the same auth backend, each one needs its own timeout policy, or you end up with inconsistent login behavior across dashboards. Second, the webhook delivery system retries failed endpoints three times with exponential backoff, but it does not notify you when all retries fail. You have to monitor the /logs/webhook-failures endpoint yourself, otherwise you might not notice a broken integration for days. The documentation covers the basic CRUD operations well, but the advanced scheduling features are scattered across three different sections of the wiki. Setting up a recurring data sync between two organizations requires combining the trigger syntax with the transformation pipeline, and there is no visual builder for it. You write the configuration as a YAML block and validate it using the /api/v2/config/validate endpoint before applying. The error messages are specific enough once you know where to look, but finding that endpoint without guidance takes effort.
If your use case involves real-time collaboration on shared workspaces, the conflict resolution mechanism uses last-write-wins with a 200ms grace period. Two users editing the same record within that window will overwrite each other silently. I found this out the hard way when a team member and I modified the same asset configuration simultaneously, and half my changes disappeared. The fix was enabling version locking in the workspace settings, which adds a slight latency penalty but prevents data loss. For most teams, the overhead is acceptable. The mobile interface works fine for viewing and basic edits, but batch operations are not supported on the app. You need to use the web dashboard for any task involving more than five records at once. This limitation is documented somewhere in the release notes but easy to miss, so I recommend checking the feature parity matrix before rolling it out to a field team that expects full functionality on their phones.
Get the Full Details
