Feature ideas

As described here , the "policy" key for entity permissions is currently supported for the "read" permission type. As part of this item, we would like to add support for create, update, and delete operations as well.

Currently, Global Filters are only supported in the UI and API. It would be great to have support for them in Terraform as well. Documentation on Global Filters: https://docs.port.io/customize-pages-dashboards-and-plugins/page/dashboard-page/#dashboard-filters

It would be helpful and practical to be able to use itemsToParse again inside each section of a multi-document YAML file For example, something like the below. resources: - kind: file selector: query: "true" files: - path: "config/repos.yaml" port: itemsToParse: .file.content | if type== "object" then [.] else . end entity: itemsToParse: .item.repos mappings: identifier: . item.name title: . item.name blueprint: '"repository"' properties: url: .item.url team: . item.team

Currently in Gitlab V2 The integration supports syncing group's members. However, this only includes members with direct membership and excludes members with inherited membership. i.e a member who has access to a group by inheriting access from a parent group. The same applies to projects, the integration does not include projects members both direct and Inherited (These are members with access to a project by being a member of a group) Proposed Improvement: To acquire full visibility into a groups and projects members, Enhance the integration to support including inherited members in projects and groups.

Currently, using the dynamic permissions feature, self-service actions will still appear in the UI. In case the user is not permitted, the run will be rejected only after sending the self-service action form. As part of this item, we would like to support hiding/displaying self-service actions using the dynamic permissions policies.

Today when mapping GitHub Users and Github teams, they are mapped separately and cannot be related (can't see which teams a GitHub user is under.) This is something that is logically expected as they are related entities in GitHub itself

Enable embedding custom widgets in Port from no/low-code platforms like Lovable and others.

Currently, to assign a swagger UI property an openapi.yaml's content, the file kind needs to be mapped with skipParsing: true, which then does not allow other properties to be assigned using jq because the content is passed as a string rather than as an object. That forces us to write to almost identical file mappings with the sole difference of skipParsing: true for the one with the Swagger UI property, and and without it for everything else basically.

Currently there is an option to add permissions only on page level I think it will be great to add on a folder level and to have the ability to inherit the permissions to the pages in the folder and to override it