- Installation and updates
- Sending your first request
- Navigating Postman
- New button
- Creating the first collection
- Postman account
- Keyboard Shortcuts
- Troubleshooting In-app Issues
- Authorizing requests
- Working with Tabs
- Visualize API responses
- Validating Requests Against Schema
- Generate code snippets
- Using GraphQL
- Making SOAP requests
- Capturing HTTP requests
- Debugging and logs
- Troubleshooting API requests
- Intro to collections
- Creating collections
- Sharing collections
- Commenting on collections
- Managing collections
- Version Control for Collections
- Using Markdown for descriptions
- Data formats
- Working with OpenAPI
- Collaborating in Postman
- Roles and permissions
- Managing your team
- Requesting access
- Team Settings
- Audit logs
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox API reference
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Building workflows
- Running multiple iterations
- Sharing collection runs
- Working with data files
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Documenting your API
- Authoring your documentation
- Publishing your docs
- Viewing documentation
- Custom documentation domains
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Intro to Monitoring
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Running Postman monitors using static IPs
- Troubleshooting monitors
- FAQs for monitors
- Intro to Workspaces
- Creating Workspaces
- Using Workspaces
- Managing Workspaces
- Viewing changelogs and restoring collections
- The API Workflow
- Managing and Sharing APIs
- Versioning APIs
- Viewing and analyzing APIs
- Validating Elements Against Schema
- Customizing Postman
- Find and Replace
- Purchasing Postman
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Configuring Microsoft AD FS with Postman SSO
- Setting a custom SAML in Azure AD
- Setting up custom SAML in Duo
- Setting up custom SAML in GSuite
- Setting up custom SAML in Okta
- Setting up custom SAML in Onelogin
- Setting up custom SAML in Ping Identity
- Intro to Integrations
- Custom Webhooks
- Microsoft Flow
- Microsoft Teams
- Publishing API documentation
Postman enables you to share Collections in Workspaces from the Postman app and the workspaces dashboard.
Note: Before you can upload or share a collection, you must sign in to your Postman account. However, you can share collections as a file without being signed in.
This topic covers:
- Sharing collections in the app
- Sharing collections in another workspace
- Sharing collections in the Dashboard
- Sharing as a file
- Modifying team permissions
- Managing requests for access
In the Postman app, select a collection in the sidebar and click the ellipsis (...) button.
Select "Share Collection".
The SHARE COLLECTION modal appears. It offers three ways to share a collection:
- Share in another workspace
- Get Link
Select this option to share a collection to another workspace or with a workspace member. If shared to a team workspace, the collection will be visible to others in the team.
You can set team default permissions to either view-only or edit; only after sharing a collection. First, you share the collection and then assign a role. You also will be able to grant existing team members individual user permissions. Remember, the Manage Roles modal will not be available until the collection is shared.
Note: Refer to Roles and permissions for more information on role-based user permissions.
In the workspaces dashboard, select a collection and then click the Share button. The collection is visible in your target workspace.
Select this option to embed a Run in Postman button in your collection for your API documentation, website, or Github readme.
The Run in Postman button lets anyone import and run this collection with one click.
When you click the Generate Code button, you get a link that you can use for a dynamic or static button. You can also select the environment you want for the generated code.
The Run in Postman button shares the collection directly from Postman, so the collection is uploaded to Postman servers when you generate the embed code.
Select this option to generate a shareable link for others to access your collections. You can manage a complete list of your collection links from your workspaces dashboard.
In the bottom bar, select "Browse", and then select a collection
Click the Share button.
In the workspaces dashboard, select "Browse", and then select a collection.
Click the Share button.
You can download collections as a JSON file to share with others, with or without signing in to your Postman account.
You can share collections anonymously, but it is strongly recommended that you sign in to your Postman account when uploading collections. When you're signed in, you can update your existing collection, make it public, or delete it later.
You can share collections with your entire team or assign individual permissions for team members. You can designate view or edit permissions for the team only after sharing a collection. Note: For now, each collection's permission must be set individually by the collection editor. The default team permission is view-only.
To assign or manage roles in the Postman app, select a collection in the sidebar and click the ellipsis (...) button.
Select "Manage Roles".
In the Manage Roles modal, select the default team permission, add a user/team member, and assign the level of permission for the user. Note: Changes made in this modal modifies the permissions of the collection.
Click the Save Changes button to complete the process.
Users can request access to a team member's personal collection or a private collection if they have a link to the collection.
To learn more about this feature, refer to the Requesting access to collections section.