Have something to say?
API key support
Allow users to generate API keys for Plotly Cloud access, making it easier to publish to Cloud from a CI pipeline or job.
Publish charts from notebooks
Add a quick action in the modebar for all Plotly charts to publish those charts directly to Cloud. Charts would be wrapped in the requisite Dash code automatically and published.
Add file upload support to Cloud
Plotly Cloud has users upload all app files for every revision. However, sometimes app contains files that don’t change from revision to revision, or files which are too large and should be separated from app source code. We would allow users to upload those files separately to their project and read from those files using a consistent path in their app. You could also write to this file store from your app if you want a persistent state from revision to revision. We would want to allow larger file sizes (e.g. up to 2gb) for each file uploaded.
Add groups for teams
Support user groups and adding user groups to apps. This makes it easier to manage a team for one organization, while sharing individual apps with specific groups that are a part of that organization.
Admin role for Teams in Cloud
Add an admin role, which is parallel to Creator/Viewer, which allows: Billing access only for admin Add/remove users only for admin Configure SSO for admin Manage roles only for admin etc.
Support app secrets
Today, we support environment variables, but we can provide native secrets support, via e.g. a secrets file, where contents are encrypted in transit. The initial scope of this ticket is to support secret storage for apps in Plotly Cloud, to be leveraged by Plotly Studio directly, but not directly exposed on the frontend. If this proves useful, we will consider adding a user-facing frontend for secrets management in a following iteration.
Fixed IP range for Cloud
Many data sources are behind firewalls that require IP addresses to be allow-listed to connect. Depending on infrastructure, this often means editing your firewall configuration. Providing fixed IP addresses for Plotly Cloud would allow allow-listing access to private infrastructure from a Plotly Cloud app.
Scheduled Tasks in Plotly Cloud
In Cloud, support running tasks outside of apps on a schedule. Cloud would add a management interface for any number of scripts, and a scheduling system to execute those scripts at regular intervals. The scripts would be able to output data to a filesystem accessible to any other apps running under the same user account in Cloud, allowing separation of data retrieval from the apps themselves.
Guest users for teams
Add a user as a viewer to a specific app without adding them to the Team overall. This special user would not be able to view apps marked, “Team: Can edit” or “Team: Can view”.
Always-on apps for Cloud
Provide support for always-on apps for Plotly Cloud rather than just on-demand apps, which sleep when no traffic hits them. This would enable apps to have fast response times even after long periods of inactivity, or to run a background process or recurring task safely.
Drag+drop to upload apps larger than 80mb
Plotly Cloud has a hard limit on app upload size of 80mb. Many Dash apps use large flat files as data sources, so this limit can prevent uploading certain projects. It’s possible today to upload a larger app using publish from dev tools.
App analytics
Show analytics on app viewership, callback usage, and more in the Plotly Cloud app viewer. Track viewing components Track per user given auth to the team Track callback usage and page viewership How long viewers are on a page Performance profiling information — page load time, refresh, slow pages…
Build rollbacks
Support rolling back to a previous build. We prevent a failing build from taking over a previously running build, but it still can be useful to roll back if a previous change was preferred.
Contact Plotly Support
Overview Users need a way to seek help in Plotly Studio or on Plotly Cloud, whether it directs them to the community forums, or Zendesk.