You are moments away from trying out Goliath and Magnus. We would like to provide you with some information before you get started.
Potens.io uses incremental authorization. We started by asking for Google Cloud Platform bigquery.readonly permission so you can use most of BigQuery features within the Potens.io.
In Goliath, you can
view your (and public) projects, datasets, tables, views, routines and models along with their metadata
run queries (SELECT), DML (INSERT, DELETE, UPDATE, MERGE) and DDL (CREATE, ALTER, DROP) statements as well as scripts
view your query history and queries statistics
and more
In Magnus, you can
create and schedule workflows using most of available Tasks such as BigQuery Task; Execute Workflow, Script and API Call Tasks; Goto, Loop and Misc Tasks and other
use built-in, custom and magic parameters
see all your Magnus inventory, execution history and execution details via Workflow and History Browsers as well as set of Dashboards
and more
Potens.io provides a wealth of actions that can be performed with initial authorization. Meantime, some actions require additional authorization in which case you will be notified along with an explanation of what permissions the action needs to proceed. You will be given the choice to grant or cancel the authorization. Additional authorization will allow you to
In Goliath
create, modify, share, and delete datasets, tables, views, routines, and models
copy tables, views, routines, and models
load data and save query results to a table, view, or Google Drive
create, copy, delete, and upload files to Google Cloud Storage
and more
In Magnus
use Cloud Storage Export Task to export data to Google Cloud Storage
attach a Google Cloud Storage file in an Email Task
use all Options within BigQuery Task such as saving to table and setting retention
execute Tasks Asynchronously
and more
If you grant additional authorization, but later change your mind, you can visit your Google Account and remove authorization for Potens.io. You will need to re-log into Potens.io and start over with the bigquery.readonly authorization.