Create and manage shared parameter standards for Informed Design products. Select parameters from your Forma hub, assign them to products, and define how their values behave in Revit projects. Ensures values update as expected when instances change.

Informed Design users can now define and generate custom output files directly from their Inventor datasets, going beyond the built-in output types to support any file format their downstream manufacturing processes require. Until now, Informed Design only supported a fixed list of predefined output types. For building product manufacturers with specialized needs, such as machine-specific data feeds, unfolded sheet metal DXFs, neutral file formats with custom translation settings, or tailored BOM exports, these built-in types often fell short. With custom output types, the output file is defined as part of the Inventor/iLogic dataset. Informed Design detects and retrieves the file on demand, uploading it to a specified destination alongside standard outputs. Why this matters Every manufacturer's downstream process is unique. Custom output types give teams full control over the data they extract from their product models without waiting for Informed Design to add new built-in output types. Whether it's a machine-specific CSV feed, an XML for a database, or a STEP file with specific translation settings applied, it's now possible to define exactly what gets generated and how. The content, format, and accuracy of each custom output is the sole responsibility of the user. Informed Design does not generate the file; it only retrieves the custom output files.   Key value and benefits Custom output types provide the flexibility to generate file type that workflows require, including CSV, JSON, DXF, STEP, SAT, XML, XLSX, and more (see full list below). iLogic provides precise control over what data gets extracted and how it's formatted, ensuring outputs align exactly with downstream manufacturing processes and business rules. Custom outputs can be individually toggled visible or hidden to low-trust team members via Output settings, providing fine-grained control over visibility and access. Once published, custom outputs can be requested directly from the IND Web App, Revit, or programmatically via the Informed Design API, giving teams multiple convenient ways to retrieve them whenever needed. How it works Custom output types are defined entirely in (as part of) the Inventor dataset. A custom output file must already exist in the dataset's root folder (or a sub-folder) before it can be selected in the Product Definition Source Content settings. iLogic rules update the custom output files using one of two methods: 1. During configuration generation: The same iLogic rules that generate the configuration also update the custom output file(s), running automatically with each configuration generation. 2. On-demand via dedicated rule (recommended): A dedicated iLogic rule with the same name as the custom output file is detected by the Informed Design Service and runs only when that custom output is requested. This method avoids running unnecessary rules during every configuration generation. With either method, Informed Design retrieves the custom output file after the iLogic rules complete. The Informed Design Service doesn't generate, translate, or validate the content of custom output files.   Supported file types Category Extensions CAD / 3D .dwf, .dxf, .glb, .gltf, .ifc, .ige, .iges, .igs, .obj, .sat, .step, .stl, .stp Manufacturing .drl, .gcode Document .pdf Image .bmp, .jpeg, .jpg, .png, .tif, .tiff Data / markup .csv, .html, .json, .txt, .xml, .zip Spreadsheet .xls, .xlsx   File checks: Informed Design confirms the file exists and isn't empty (0 KB) before it can be added. It doesn't inspect the file's internal format or content beyond that. Duplicate handling: Custom output files with the same file name cannot be added, even if they exist in different folders. Informed Design flags these as duplicates. Per-file visibility: Each custom output file can be independently toggled visible or hidden to low-trust members in Product Definition Output Settings, so some outputs can be broadly available while others stay restricted. Removing outputs: Removing a file from the Publisher's output list (individually or via Clear all) only updates the product definition. The file itself is left untouched in the project folder.   How to use it (today) - Inventor Create the custom output file(s) and include them in the root folder of the Inventor project (or a sub-folder). Write iLogic rules to update the custom output file(s). You can use either approach: Automatic updates: Rules that run during configuration generation and update the output files On-demand execution (recommended): Dedicated iLogic rules with names matching the custom output file names. The Informed Design Service detects these rules and executes them only when the corresponding output is requested. In the Product Definition, go to Source Content and click Select Files to add the custom output files the same way drawing templates are selected. In Output Settings, toggle on the custom outputs to make available to low-trust members. Publish the product definition. Generate custom outputs from the IND Web App, Revit, or via the Informed Design API. Example iLogic Rules The attached zip folder contains working examples of dedicated iLogic rules (rule name = file name). Copy the code into an iLogic rule, name the rule to match the desired output file name, and the Informed Design Service will detect and execute it only when that output is requested.   Known limitations Custom output types have the following constraints and limitations. User responsibility for content and accuracy: The content, format, and accuracy of each custom output file is the sole responsibility of the user. Informed Design does not generate or validate the file; it retrieves the file as-is. Verify iLogic rules before publishing to ensure they correctly produce the desired output. Inventor datasets only. Custom outputs are supported for Inventor-based product definitions. Fusion support is not available in this release, as the feature depends on Inventor's iLogic-driven automation. Fixed output file names required. Output file names must be fixed and predefined. Dynamically named or variable-quantity output files are not supported. Each output file path must be known in advance and remain consistent across all configuration variations. Part and sub-assembly files not supported. Part files (.ipt) and sub-assembly files (.iam) from the base model assembly cannot be used as custom output types. Only standalone files in supported file types in the dataset's root folder can be selected as outputs. Filename collisions across folders. Two custom output files cannot share the same file name, even if they are located in different folders. Informed Design will block duplicate file names and prevent both from being added. File removal does not delete source files. Removing or clearing custom outputs from the Publisher only updates the product definition's output list. The underlying files are not deleted from the project folder. Missing outputs are silently omitted. If no custom output files are selected in Source Content, no custom output type is generated for that release. There is no error message; the option is simply unavailable to request. Excel (.xls / .xlsx): iLogic rules must use the LibXL engine for Excel output (Excel COM automation does not work in Design Automation). In Inventor, configure this by opening Zero Document Mode, navigating to Options > Advanced iLogic Configuration, and setting Excel Engine to LibXL. (LibXL is the default on DA4i.) - Note: LibXL supports external Excel files only; embedded Excel files are not supported. FAQ Can custom output types be used with Fusion-based products? Not yet. Custom output types depend on Inventor's iLogic rules running through Design Automation for Inventor to keep the output file current. Fusion doesn't yet have an equivalent automation path, so support is deferred for now. What file types can be used for a custom output? See the supported file types table in the How it works section above. Does Informed Design validate the contents of custom output files? No. Informed Design only checks that the file exists and isn't empty (0 KB). It doesn't validate the file's format or content. Accuracy of the output is the user's responsibility. What happens if two files with the same name are selected from different folders? Informed Design treats them as duplicates and prevents both from being added, even though their folder paths differ. If a custom output is removed from the Product Definition, is the file deleted? No. Removing an output, including using the Clear all button, only updates the product definition's output list. The file itself stays untouched in the project folder. Is there a limit to the number of custom output files that can be added? There's currently no fixed limit. Can individual custom outputs be made visible to low-trust members while keeping others private? Yes. Visibility is controlled per custom output file in Output Settings, so outputs can be selectively shared or restricted. Why does my iLogic rule not run when I request the custom output? Verify that the rule name matches the output file name exactly (including the file extension). The Informed Design Service uses the rule name to detect and trigger the rule, so any mismatch will cause it to be skipped. Get started Custom output types are available now for Inventor-based product definitions. To get started: Open the Inventor dataset. Prepare the custom output files and iLogic rules (use the examples provided as templates). Select the custom output files in the Source Content tab of the Informed Design Publisher. Publish the product definition. Request custom outputs from the IND Web App, Revit, or via the Informed Design API. This experience will continue to be refined, and feedback is valued. For questions, suggestions, or ideas for improvement, leave a comment below or visit the Informed Design Forum to join the conversation.  

Informed Design users can now open Data Exchanges created from Revit projects, directly in the Informed Design web app.   Until now, opening Revit-based content in the Informed Design web app required uploading the entire Revit project to Autodesk Forma Data Management (formerly known as Autodesk Docs). While that provided access to all Informed Design instances in the project model, it also meant sharing the full project file even when collaborators only needed a smaller subset of content.    With this new capability, teams can create and open Data Exchanges that contain only the relevant Informed Design instances needed for a specific workflow, supplier, or coordination task.    Why this matters    Project teams and building product suppliers often do not need access to the entire Revit model. In many workflows, sharing only the relevant Informed Design instances is simpler, more efficient, and easier to manage.    Key value and benefits    By using Data Exchanges as a source for the Informed Design web app, teams can now: Share only the relevant product variant instances Simplify collaboration between suppliers and stakeholders Reduce the overhead of managing full Revit project uploads Generate outputs from a more focused subset of content   Teams can continue working from full Revit projects when needed, or use Data Exchanges for more targeted workflows.     Try it out   1. Open a project containing Informed Design product instances in Revit on your desktop.    2. Create a new 3D View that contains the Informed Design instances you want to include in the Data Exchange. Hide any elements you do not want included.    3. With the 3D View active, go to the Collaborate ribbon tab and click on the Data Exchange command. If you have not done so already, you'll need to install the Autodesk Data Exchange Connector for Revit first.     4. In the Data Exchange dialog, click Create.   5. Enter a name and select a save location. Make sure the selected view is the 3D view you created in step 2, then click Create Exchange.      6. In the Informed Design web app, navigate to the Hub, Project, and Folder where the exchange was saved in step 5. Select the Data Exchange file (DX) and click Open Model.      7. The model will display only the instances and elements you included in the Data Exchange, based on what was shown in the 3D view you created in step 2.        This enhancement gives teams a more flexible way to route Informed Design content from Revit into downstream workflows, while limiting shared content to only what is needed.   

Learn more about how BIM subcategories authored in Inventor enable Informed Design to deliver Revit families with native visibility and graphics control.

There’s a moment on many projects where momentum pauses. Someone asks “Is this dimension allowed?” At that point, the process shifts into static reference materials, a BIM tool, or an engineering review.   That shift is manageable for architects and designers, since they already use the Informed Design Add-in for Revit to configure products within the supplier’s allowable range – but the buying process doesn’t stop with the architect. Clients, procurement teams, and other project collaborators want to evaluate options for a product outside the BIM authoring context.   With the new Informed Design APS Viewer Extension, that same rule-driven validation designers access through our Revit Add-in is now available directly in the web browser.   The Foundation: Autodesk Platform Services Viewer   If you’ve used the Autodesk Viewer through Autodesk Docs (soon to be Forma Data Management), Fusion Team, or Shared Views functionality, you’re already familiar with high-performance 3D model viewing in the browser.   Our Informed Design Viewer Extension is built on that same APS Viewer SDK to enable not only visualization, but rule-driven product configuration and BIM-ready output generation, directly in the browser.   For Product Suppliers   As a supplier publishing products using the Informed Design Add-in for Inventor, you can now open your published releases in the 3D web viewer.     Open a release and preview variants in the web browser   Open the Informed Design Web Portal. In the header navigation, select the Forma hub and project that host your products, then open the Releases tab. Note: Project Admin–level permission in the Autodesk Docs (Forma Data Management) project is required to access the Releases tab. Select a product from the list on the left, then choose a release from the table. Note: Products appear based on the folders selected in the Folders filter. If the list is empty, click the Folders filter button above the list. In the Filter products by folder dialog, select at least one project folder containing published products and click Apply. Open the release: Click View in 3D at the top of the Releases table. The Informed Design APS Viewer Extension opens in a new browser tab and loads the selected release. The Informed Design toolbar appears on the far right of the viewer, after the APS Viewer’s standard navigation and selection tools. It includes the following options: Release details – Displays read-only summary information such as the release date and Revit Family (.rfa) output's Category. Form – Shows the release’s input parameters, values, and controls, which are editable when the release’s configuration rules allow it. Variants – Opens a table listing all variants created for the release. From here you can access the web-viewable (.svf) outputs of completed variants and monitor those still in progress. Preview existing variants: Click the Variants toolbar button to open the variants table. Select any row to display that variant in the 3D viewer.   Configure variants and track output status   If the release is Configurable, you can use the Form to create new variants directly in the 3D viewer. Each validated configuration you generate in the browser automatically becomes BIM-ready content, building your Revit Family (.rfa) library as you go.   Open the configuration form: Click the Form toolbar button to display the release’s configuration form. Note: For releases published as Static, form controls are read-only. Open the Variants table to browse the supported configuration in its available model state representation(s). Create a variant: Use the form controls to select the desired values. Once the configuration passes validation rules, click Generate to create the variant. Note: If a release has the Obsolete status, it can still be opened in the viewer and existing variants can be previewed. However, form controls and the Generate button are disabled because new outputs cannot be created from an obsolete release. Open the Variants dialog. After you submit a configuration, a new row appears in the Variants table. Track variants in progress. Two columns track output status: SVF shows the status of the web-viewable model displayed in the browser. RFA shows the status of the generated Revit Family (.rfa). For variants that support Revit output, both the web-viewable (.svf) model and the Revit Family (.rfa) are generated in parallel. Identify BIM-ready variants: When generation completes successfully, a checkmark icon appears in the status column: When the variant's SVF column is checked, the web-viewable model is displayed in the browser. When the variant's RFA column is checked, designers with permission can immediately load that Family into their Revit projects through Informed Design's Revit Add-in. This relationship works both ways – when a designer generates a variant .rfa using the Informed Design Add-in for Revit, the corresponding web-viewable .svf is created automatically and appears in the 3D viewer's Variants list.   Variants created through the API   In some releases, the Variants table may contain rows where the Representation column shows “Not specified”, and the SVF and RFA columns display question-mark icons. This occurs when a variant was created through the API. API-first variants do not require a representation when they are generated (see POST /variants). However, both the .svf (web-viewable model) and .rfa (Revit Family) outputs depend on a representation (see POST /outputs) so their availability cannot be determined automatically. To resolve this, open the Form and select a representation from the dropdown menu in the dialog footer. The dropdown lists the representations available for the .svf output type. Then click Generate to display it in the viewer. If the selected representation also supports .rfa output, the Revit Family will begin generating in parallel and you’ll see a progress spinner. If it does not, the RFA column will display a ban icon (circle with a dash), indicating that .rfa output was not made available for that representation in the current release.   For Developers and Partners   The Informed Design Viewer Extension is also available as an embeddable component. This allows suppliers to integrate interactive 3D product exploration directly into their own web platforms.   Access the Viewer SDK and reference materials in this repository.    The README provides the information needed to get started. For more detailed implementation guidance, refer to the Informed Design Viewer Extension docs.     Still have questions? Leave a comment below or visit the Informed Design Forum. 

Learn how new panels in the Informed Design Add-in for Revit surface product structure and metadata to make bulk actions easier, usage clearer, and design decisions more predictable.

Informed Design Inventor Add-in Installation    To set up Informed Design for Inventor so you can author and publish product models for use within Revit follow these steps after installing Inventor 2024.2 or later:  Go to informeddesign.autodesk.com and log in using your Autodesk account credentials.   Click on   in the title bar and choose Informed Design Add-in from the drop-down menu or go directly to Informed Design Add-in for Inventor.     Click on the Inventor tab. Select Download Add-in for your Inventor version year. We support Inventor 2024, 2025 and 2026.     Click on the downloaded file named Informed Design Add-In X.XX.X.X for Inventor 202x.msi to launch the Informed Design Add-In Setup Wizard.     Follow the installation Wizard instructions to complete the add-in installation process.  **Make sure Inventor is not currently running before installing this add-in.**     Informed Design for Revit Add-In Installation To set up Informed Design for Revit so you can discover and design with published product models from Inventor, follow these steps after installing Revit 2024.2 or later: Go to informeddesign.autodesk.com and login using your Autodesk account credentials. Click on   in the title bar and choose Informed Design Add-in from the drop-down menu or go directly to the Informed Design Add-in for Revit.   Click on Revit tab.   Select Download Add-in for your Revit version year. We support Revit 2024, 2025 and 2026. Click on the downloaded file named Informed Design Add-In X.X.X.X for Revit 202x.msi to launch the Informed Design Add-In Setup Wizard.   Follow the installation Wizard instructions to complete the add-in installation process.  **Make sure Revit is not currently running before installing this add-in.**      

What's New?   Previously, Revit users had to leave the Revit project context to generate manufacturing output files from instances of Informed Design Families. To obtain 2d drawings, bills of materials, native 3D datasets, and neutral CAD files from Family instances, you had to upload your Revit model to an ACC project folder and open it in the Informed Design Web App. We've now made it possible to request these output file types directly in Revit, at any stage of design maturity – no need for ACC sync!     Use the new Generate Outputs command in the Informed Design ribbon to request supported deliverables without leaving your model. Single-instance selection (today): You can select one instance in the canvas and request outputs for that instance’s release and variant. Why this matters Until now, Revit users had to leave Revit to request output files from Informed Design instances. That meant context-switching, extra coordination, and—often—a long wait while the Revit model syncs in ACC.   Previous Workflow: 1. Place Informed Design instances in your Revit model. 2. Publish the RVT to ACC (processing can take up to 24 hours). 3. Sync with Central to update the ACC model (typically 30–45 minutes). 4. Launch the Informed Design web app and open the Revit model from ACC. 5. Select the desired instances, and set up and submit the request for outputs.   By enabling output generation inside Revit, we remove many steps, reducing friction. Output generation in Revit provides easy access to output files, even when the Revit model is not yet ready to share with project collaborators in ACC.     Benefits   For new Informed Design users Try the full end-to-end workflow, natively in Revit Request outputs and access the uploaded results within minutes—ideal for pilots, training, and proof-of-value. For designers (Revit users) Less context-switching: design, validate, and request outputs in one place. Faster iteration: confirm downstream impacts earlier (BOM, spec sheets, drawings). For vertically integrated firms Tighter feedback loops: designers can generate the documentation manufacturing needs, earlier in the cycle Smoother handoffs: reduce back-and-forth when coordinating with manufacturing/fabrication teams.     How to use it (today) In Revit, place an Informed Design product and select a single instance in your view. On the Informed Design ribbon, choose Generate Outputs. Pick from the outputs the publisher made available for that release (for example: Bills of Materials, spec drawings, cut sheets, etc.).   What you can generate?   Availability is set by the product publisher at release time. Typical downstream outputs include: Bills of Materials Product/assembly specification drawings Neutral CAD formats: STEP files for example   For more information about controlling output availability as a Product Publisher, check out Changes to Access Permissions here.     FAQs Does this replace the web app? No. The web app remains essential for broader administration, analytics, and advanced flows. The Revit-side generate feature is focused on speed and iteration for day-to-day design work and first-time trials.   Where do the files go? Your files will go to the existing destinations applied, typically ACC Docs folder where the Revit project is located.    Why can’t I select multiple instances yet? This initial release prioritizes reliability and simplicity. Multi-selection and project-wide runs are actively in development.   What if an output type I need isn’t listed? Output availability is defined by the product publisher per release. Ask your manufacturer/publisher contact to mark the relevant representations/templates as available. Get started Try it now in Revit with Autodesk Sample products (switch the Public Content toggle On in the Revit Add-in Insert dialog.) Share feedback on what would make this truly end-to-end for your team. If you publish products, review your output templates and availability settings to ensure designers can generate what they need from inside Revit.   Feedback? Leave a comment here or create a post in the Informed Design Forum.

As we expand support for publishing to non-US Autodesk Construction Cloud (ACC) accounts, our users based outside the US have asked important questions about where data is stored, when it’s processed, and what regional implications that might have. This article outlines how Informed Design stores and processes product-related data, what role ACC plays in access control, and why no building project data ever leaves your region — even when publishing or using products linked to non-US based ACC accounts.   All Product Data Is Stored and Processed in the US   All product-related data in Informed Design is stored in our US-based Informed Design service and processed using our US-based APS Automation services. This includes: CAD files or model references Parameters and rules Product variations (configurations and model state representations) Output file definitions (such as Revit Families and bills of materials)   At the time of publishing a new product or a product update, users of the Informed Design Add-in for Inventor are shown a clear notice:  By using Informed Design, your project data may be processed and stored in the US.   The notice also mentions the following limitation:  Currently, Bridge functionality is supported for Informed Design products published in US-based accounts only. This means that as of now, ACC Bridge folder automations between non-US based ACC projects will omit Informed Design products. All other files will sync as expected.   What About Non-US ACC Accounts?   Informed Design integrates with ACC — the Files tool in Autodesk Docs — to manage access permissions, not for file storage or data regionalization. This lets your team use the familiar ACC environment to control who can work with your published products in the Informed Design Add-in for Revit and the Informed Design Web Portal.   You can now publish to any Docs project folder, regardless of the ACC account's regional data storage.    ⚠️ Important: Publishing to an ACC account based in the EU, Australia, UK, Germany, Canada, India, or Japan does NOT mean product data is stored or processed in that region.    When Does Data Enter the US?   New user-defined data is submitted to our US-based service only at a few specific points.   When the user publishes a Product or Release: Creating a Product (POST /products) Updating a Product (PATCH /products/{productId}) Creating a Release (POST /releases) Updating a Release (PATCH /releases/{releaseId}) These publish-related actions send and persist your product definition, CAD files or model references, input parameters, and output types to our Informed Design service, hosted in the US. When the user submits a Variant: Create Variant (POST /variants) This action sends and persists your specified parameter values as constrained by the published product release, and in some cases, your chosen variant name. Our US-based APS Automation services use this information to build your requested variant on-demand using the CAD dataset. Variant creation submits no new user-defined data to US-based services other than your request parameters, and variants contain no reference to specific building models or Revit files.   When a user requests Output creation based on a Variant : Create Outputs (POST /outputs) This action sends and persists the alphanumeric identifier of the variant you've specified, and your choice of output types (such as a Revit Family or shop drawings) to be created from that variant.  Our US-based APS Automation services use this information to create your requested output file on-demand using the previously-generated variant. As you'll see in the payload schema, output requests submit no user defined-data to US-based services other than your choice of variant and output file types.   When a user requests file upload based on an Output : Create Upload Request (POST /uploads) This action sends and persists the alphanumeric identifiers of the outputs you've specified, and your choice of upload location for the resulting files. Our US-based Informed Design service uses this information to create files using your previously-generated outputs and place them into your selected ACC or Fusion Team folder. Upload requests submit no user-defined data to US-based services other than your choice of outputs and folder for the uploads.   What Happens in Downstream Workflows?   Once a product and its releases are published, the additional workflows described above use our US-based services, but do NOT introduce any building design or project-specific data to our system.   Instead: Variants are created by modifying parameters and model states of the already-published release; no building-specific context is involved. Outputs (Revit Families, shop drawings, etc.) are generated from those variants using our APS Automation engine, based on already-published product and release data. Uploads refer to our service placing generated output files into your selected ACC or Fusion Team folder; no incoming files are transferred from your building project. No Revit models, building geometry, or project-specific design context are ever uploaded to or processed by the Informed Design or APS Automation services.   What This Means for Data Privacy and Sovereignty   Even when publishing to a non-US ACC account: Your building project files stay in your region by design, thanks to ACC Regional Data Storage.  Your published product data is stored and processed in the US. After publish time, all downstream activity is driven by users acting upon the already-published product and release data. With this architecture, your building project-specific information remains within your chosen ACC data region.   For Developers and Partners If you want to dive deeper into exactly what data is transmitted, when it’s sent, and how each request is structured, our full API documentation provides a complete technical reference — including endpoints, payload schemas, and response formats.   Explore the Informed Design API Reference.   We hope this helps you and your team make legally and operationally compliant decisions when working with Informed Design across international projects. Still have questions? Leave a comment below or visit the Informed Design Forum. 

We’re excited to share a major milestone in the Informed Design workflow — our first publicly discoverable content experience is launching in Revit!    With this feature: Building product manufacturers will be able to share their published Informed Design products with the general public instantly, with literally the flip of a switch. Revit users, like architects and engineers, can discover these public Informed Design products, customize them according to the manufacturer's pre-defined rules, and use them in Revit projects — without needing ACC access at all.   Why Public Content?   Benefits for Publishers   Up until now, as a manufacturer publishing Informed Design products, it was only possible to share them with architects, designers, and other consuming audiences in two ways:    Direct Project Folder Access: Invite each individual to the product's ACC project folder by email. This option requires every recipient's email address. ACC Bridge Outgoing Automation: Set up an Outgoing sync between your product's ACC project folder and each recipient's ACC project, so their project members can access your published products.  This option requires knowing each outside firm's ACC project, to create the Bridge syncing data from yours to theirs. But what if you want to share your products with anyone who might be interested in using them – without having to know exactly who they are in advance?    With the new Public setting, manufacturers can share Informed Design products with minimal administrative effort – no manual invites, and no more ACC access requirements or folder permission checks standing in the way of their products' potential audience.   Benefits for Consumers   Previously, as an architect or designer using Informed Design in Revit, you needed both an ACC subscription and specific project folder permissions to access published products – either as a direct member of the ACC project folder or via ACC Bridge Incoming Automation.    The new Public setting for published products removes those hurdles and opens product discovery to everyone:  No ACC Access Requirement: Access public Informed Design products without being invited to an ACC project folder, and without being an ACC user at all.  Streamlined Product Browsing: Browse all publicly discoverable Informed Design products in a single list in the Revit Add-in, with options to filter by Publisher or Revit Category.    How to Access Public Content   As a Publisher   👉 Ready to make your products public? Join our tech preview: Get started here.    Publishers participating in the tech preview follow the process below to share their products publicly.   Create a Publisher: For each manufacturer, our team is creating a new Publisher profile under their chosen brand or business name, and links that Publisher to the manufacturer's designated ACC account. From then on, every product published to project folders in that account will be eligible for public sharing. Publish Products with Appropriate Output Availability: In the Informed Design Add-in for Inventor, set the output availability carefully. Output files can be requested by the Permission-Unenforced audience from any representations and drawing templates you set to Available (toggle On) on the Outputs tab. The Permission-Unenforced audience includes recipients of ACC Bridge Outgoing Automation, and the general public when the product's Public setting is switched On. Share Products Publicly: Each product published in the Publisher-linked ACC account will have a Public toggle in the Informed Design Web App, located in the product administration UI on the Releases tab. When the Public toggle is switched On, the product becomes available in the Informed Design Add-in for Revit. In the Revit Add-in, the product is listed under the manufacturer's designated Publisher name, and both the Permission-Enforced and Permission-Unenforced audiences can design with any of its usable (non-Obsolete) releases.   As a Consumer   👉 Architects and designers using the Informed Design Add-in for Revit can start browsing public content today!   New products will become available in the upcoming weeks as publishers join our tech preview and start sharing. Here's how to discover and use them.   Design with Public Products: In the Insert dialog of the Informed Design Add-in for Revit, turn on the Public Content toggle to display all products shared publicly by manufacturers. Public products can be refined by Revit Family Category or by Publisher using the dropdown menus. After selecting a public product release, any designer can customize it to create variants, and insert those variants into their Revit projects as RFA – with no ACC access needed.  Request Outputs from Public Products: Anyone accessing a public product can request files from output representations and templates the publisher marked as Available at publish time, without any ACC permission checks. Select an instance of a public product, then activate the Generate Outputs command on the Informed Design ribbon. If the command is enabled, a dialog will let you choose from the non-RFA outputs available for the release. Results of these output requests are uploaded to a designated folder in ACC Docs or Fusion Team – you will need access to either ACC or Fusion Team to view and download these files.   Changes to Access Permissions   👉 To simplify the administration of published Informed Design products – both privately and publicly shared! – we've altered our access permissions model to better align with authorization in the Informed Design API.    A product may be accessible to a Permission-Enforced audience only, or to the Permission-Unenforced audience as well, depending on how its access is currently scoped.   Permission-Unenforced Access In the Permission-Unenforced access mode, we do not check the ACC project folder's member list in the origin project before granting access to the product.    ACC Bridge Access (Public = Off): the Permission-Unenforced audience includes individuals with indirect access to the product's ACC project folder, as recipients of an ACC Bridge Outgoing Automation. Public Access (Public = On): the Permission-Unenforced audience is the general public. Anyone can access the product without logging into ACC. The Permission-Unenforced audience can request outputs from any representations and templates that were set to Available (toggle On) for the release on the product definition's Outputs tab.   Permission-Enforced Access In the Permission-Enforced access mode, we confirm that the user is on the ACC project folder's member list before granting access to the product.    The Permission-Enforced audience for a product includes only individuals with direct access to the product's ACC project folder, as project members with sufficient folder-level permission. The Permission-Enforced audience can request outputs from all representations and templates that were listed for the release on the product definition's Outputs tab, including those set to Unavailable (toggle Off.)     Impact of output type availability in the product definition.     Feature Availability for Permission-Enforced Access Users   This chart lists the features available to the Permission-Enforced audience at each access level.   Each access type in the Informed Design API is listed with the minimum ACC project folder permission needed to meet its authentication criteria.   Feature Availability for Permission-Enforced Access Users   Still have questions? Leave a comment below or visit the Informed Design Forum.   

Advance your Informed Design Codeblock skills! Learn how to dynamically update Minimum and Maximum input values

Understand the fundamental Revit skills required to make the best use of the Autodesk Informed Design add-in for Revit.

Learn how to use Informed Design Codeblock functions to simplify and speed up logic creation with reusable code modules.

Use this checklist to help prepare your existing configurable Inventor models for publishing to Autodesk Informed Design.

Uncover the details behind what the product development team is tackling now, next and later for Informed Design.

Read on for detailed information about the requirements, advantages and disadvantages of the Configurable and Static product publishing methods in Informed Design. 

Eight quick tips to help you build and publish Inventor models to Autodesk Informed Design with ease!

Learn what's new in Autodesk Informed Design for August 2024, including support for ACC Bridge, streamlined RFO experience, New BIM definition workflow, and publish prerequisite checks.

Codeblocks Best Practices: Codeblocks empower users to create code through an intuitive drag-and-drop interface, eliminating the need for traditional text-based programming. 

Learn what's new in Autodesk Informed Design for May 2024, including support for outputs to Fusion team, revised Revit Replace and Update commands, and a new Form Design workflow in Inventor.