Port
Create
Log in
Sign up
Roadmap
Feedback
Feature ideas
Changelog
Boards
Feature ideas
Powered by Canny
Feature ideas
We take your ideas seriously! Read more on our prioritization process in our blog
https://productmanagement.port.io/posts/managing-feature-ideas
Details
Category
Select a category
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Exploring
Planned
In Progress
Complete
posts in
All Categories
All Categories
Audit log (28)
Automations (47)
Dashboards & widgets (228)
Data model (180)
Data sources (156)
Integrations (392)
Navigation & global search (52)
Scorecards (45)
Self-service actions (315)
Entity Pages (61)
Catalog Tables (105)
RBAC & Ownership (56)
Organization Management (69)
AI agents (51)
Product Security (12)
Authentication & users (48)
Workflows (30)
Port AI assistant (4)
SIEM Integration for Port's Audit log
Some customers would like the option to automatically report Port's information to an external SIEM system for security concern. https://www.ibm.com/topics/siem#:~:text=Security%20information%20and%20event%20management,chance%20to%20disrupt%20business%20operations . First and most important are the changes of Port's audit log
7
·
Audit log
55
Expose Catalogue Usage Telemetry
As a Platform Engineer launching a new dashboard in the Port catalogue I'd like to 1) track adoption and usage of the new dashboard/page and 2) have access to data so I can integrate my surveying tooling to survey the users who use the new dashboard. For big picture context. We are also a customer of DX who have a product called PlatformX. We have integrated this into our Self Service Actions. When a user (Bob) runs a self-service action via Port an event is fired off to DX saying that Bob did X event. DX looks to see if Bob is eligible for surveying based on the action (event) taken and if valid will send a survey to them personally on teams (MS Bot framework). This gives a very low friction option for Bob to provide feedback they might have otherwise not raised. We'd like to perform a similar integration but for important pages in the catalogue, like a newly launched dashboard. So, the user experience might be that Bob accesses the new port dashboard page for the first time and sometime later is pinged on teams saying "Hey we saw you used the ABC dashboard for the first time. Could you let us know what you thought etc..." Currently we don't have access to data that tells us who has accessed what pages in the catalogue at what time. Could this data/event telemetry be made available?
0
·
Audit log
13
Show login attempts in the audit log
Make it possible to see login attempts (both successful and unsuccessful) in an organization's audit log
3
·
Audit log
11
Ability to specify the source of an API change (updatedByAlias/createdByAlias)
We now have multiple locations where we are using the API to update specific blueprints. Having all changes to blueprints made through the API under "Rest API" is too vague for us to know where specifically the change came from. It would be nice if we could include a name of the source in our blueprint change payload and then be able to see this reflect in the audit logs. For example: I change blueprint Service with a python script called "service_ changer.py " using a POST in the script - I can also pass into the body of the POST "updatedByAlias":"service_ changer.py " And then later, I can filter the audit log by "updatedByAlias":"service_ changer.py " to see all changes made through that specific script.
0
·
Audit log
11
Audit Log for Pages
Provide audit log functionality for pages so that we can track which users create/edit/delete things like dashboards.
0
·
Audit log
9
Update audit log for Users & Team entities to show what user made the change
Currently I can see that a change to a User or Team was made, I cannot see who made it. The audit log record only shows "updated by": "port-internal" as in the screenshot as opposed to an actual user. This is important for compliance auditing
2
·
Audit log
8
Actions audit log improvements
In addition to the general action runs audit log, a specific audit log for each action will be added to the "audit log" page Each action log will display as columns the general details of each run (ID, status, start, end) and also the specific inputs of the action inputted by the user who executed it.
1
·
Audit log
7
Action runs - update log messages.
Currently, there is no way to edit current action logs. A possible solution will be to return a message ID when posting a log through the API, and implementing a new route to patch messages based on the ID. This will help keep the logs cleaner and save a lot of space.
0
·
Audit log
7
Audit log for user management
Capture user management activities (names and time stamps) in the audit log. For example: when user was invited / created / deleted who invited / edited / deleted user when user permissions changed who changed user permissions how the user was created (API, UI, etc)
0
·
Audit log
7
Client Secret Rotation Alert
We want to configure an alert that is sent out to admins when an organization secret has been changed. Or perhaps, a way to subscribe to a Port event that says “this client’s secret was rotated.”
0
·
Audit log
7
Load More
→
Powered by Canny